cold-coat-35200
02/25/2019, 9:15 PMproud-tiger-5743
02/25/2019, 9:46 PMconst taskRole = new aws.iam.Role('foo',{})
const task = new awsx.ecs.FargateTaskDefinition('bar',{})
I'm trying to build a lambda role that can has perms to
{
Effect: "Allow",
Action: ["iam:PassRole"],
Resource: [taskRole.arn]
},
{
Effect: "Allow",
Action: ["ecs:RunTask"],
Resource: [task.taskDefinition.arn]
}
But I can't seem to find a combination of apply or pulumi.all that allows me to generate the JSON input into the role. Any ideas?proud-tiger-5743
02/25/2019, 10:17 PMlemon-greece-30910
02/25/2019, 11:05 PMDockerfile
with awsx.ecs.Image.fromPath
as show in the example on https://pulumi.io/quickstart/aws/tutorial-service.html ... i would like something similar so i can build an image for kubernetes to work on an example like shown at: https://github.com/pulumi/examples/tree/master/kubernetes-ts-exposed-deployment.
i have tried searching the documentation but i am unable to find what i am looking for. perhaps i am searching in the wrong place?early-musician-41645
02/26/2019, 12:32 AMtall-librarian-49374
02/26/2019, 9:16 AMerror: Error: failed to register new resource hello-world4fcc7b60 [aws:lambda/function:Function]: 8 RESOURCE_EXHAED: grpc: received message larger than max (6953666 vs. 4194304)
for https://gist.github.com/mikhailshilkov/8b6b035e94c5b46b34605fac6a2691betall-librarian-49374
02/26/2019, 9:41 AMaws.apigateway.x.API
route to a aws.lambda.Function
? @lemon-spoon-91807busy-daybreak-68237
02/26/2019, 11:35 AMfaint-vegetable-61837
02/26/2019, 2:14 PMpulumi up
with Ctrl-C, and next time I ran it I got this:
error: an unhandled error occurred: Program exited with non-zero exit code: 1
The Pulumi runtime detected that 16 promises were still active
at the time that the process exited. There are a few ways that this can occur:
* Not using `await` or `.then` on a Promise returned from a Pulumi API
* Introducing a cyclic dependency between two Pulumi Resources
* A bug in the Pulumi Runtime
Leaving promises active is probably not what you want. If you are unsure about
why you are seeing this message, re-run your program with the `PULUMI_DEBUG_PROMISE_LEAKS`
environment variable. The Pulumi runtime will then print out additional
debug information about the leaked promises.
error: an error occurred while advancing the preview
Canot find anything in the docs on how to move forward from this. My stack is not creating promises, so it must be Pulumi components...faint-vegetable-61837
02/26/2019, 2:43 PMpulumi logs
does not print anything, no matter which flags I pass to pulumi (-v 3, etc)proud-artist-4864
02/26/2019, 2:46 PMproud-artist-4864
02/26/2019, 2:48 PMaverage-summer-30977
02/26/2019, 3:33 PMworried-engineer-33884
02/26/2019, 3:48 PMaws.secretsmanager.getSecret
and pass that into an input for DMS endpoint credentials, are the values stored in pulumi state? are they encrypted?worried-engineer-33884
02/26/2019, 3:55 PMpulumi login --local
?better-rainbow-14549
02/26/2019, 3:57 PMbetter-rainbow-14549
02/26/2019, 3:57 PMbusy-pizza-73563
02/26/2019, 5:47 PM<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
label to all my k8s resources (probably because of https://github.com/pulumi/pulumi-kubernetes/commit/f23736ef49b83864a518e8c34135a466ca1f1588). Is there a way to opt-out?orange-policeman-59119
02/26/2019, 7:22 PMComponentResource
? I would like the component to take a namespace to install into as an argument, but I can't figure out how to extract the name
of the namespace out of a k8s.core.v1.Namespace
object.orange-policeman-59119
02/26/2019, 7:23 PMworried-engineer-33884
02/26/2019, 9:08 PMchilly-photographer-60932
02/26/2019, 9:54 PMexports
lemon-greece-30910
02/26/2019, 10:26 PMfromPath
in the latest version (0.16.5) requires 2 parameters. but i can not figure out how the second parameter should to be specified. it would be helpful anyone is able to provide an example.gray-greece-11354
02/26/2019, 11:02 PMgray-greece-11354
02/26/2019, 11:03 PMbusy-umbrella-36067
02/26/2019, 11:47 PMThe Pulumi runtime detected that 200 promises were still active
at the time that the process exited. There are a few ways that this can occur:
* Not using `await` or `.then` on a Promise returned from a Pulumi API
* Introducing a cyclic dependency between two Pulumi Resources
* A bug in the Pulumi Runtime
enough-judge-17725
02/27/2019, 12:04 AMenough-judge-17725
02/27/2019, 12:04 AMenough-judge-17725
02/27/2019, 12:05 AM