helpful-advantage-49286
05/13/2019, 6:35 PMhelpful-advantage-49286
05/13/2019, 6:36 PMhelpful-advantage-49286
05/13/2019, 6:36 PMhelp.domain
to some.other.domain
salmon-account-74572
05/13/2019, 6:39 PMhelpful-advantage-49286
05/13/2019, 6:40 PMsalmon-account-74572
05/13/2019, 6:44 PMsalmon-account-74572
05/13/2019, 6:45 PMhelpful-advantage-49286
05/13/2019, 6:45 PMhelpful-advantage-49286
05/13/2019, 6:45 PMhelpful-advantage-49286
05/13/2019, 6:45 PMhelpful-advantage-49286
05/13/2019, 6:45 PMsalmon-account-74572
05/13/2019, 6:46 PMbetter-rainbow-14549
05/13/2019, 7:12 PMbetter-rainbow-14549
05/13/2019, 7:13 PMfull-dress-10026
05/13/2019, 7:25 PMtags
for awsx.ecs.FargateService
. Was there a reason this was omitted?helpful-advantage-49286
05/13/2019, 7:31 PMhelpful-advantage-49286
05/13/2019, 7:31 PMhelpful-advantage-49286
05/13/2019, 7:51 PMfreezing-flag-53289
05/13/2019, 9:26 PM❯ go test -v
go: finding <http://github.com/pulumi/pulumi/pkg/testing/integration|github.com/pulumi/pulumi/pkg/testing/integration> latest
go: finding <http://github.com/pulumi/pulumi/pkg/testing|github.com/pulumi/pulumi/pkg/testing> latest
go: finding <http://github.com/pulumi/pulumi/pkg|github.com/pulumi/pulumi/pkg> latest
go: finding <http://github.com/Nvveen/Gotty|github.com/Nvveen/Gotty> v0.0.0-20170406111628-a8b993ba6abd
go: <http://github.com/Nvveen/Gotty@v0.0.0-20170406111628-a8b993ba6abd|github.com/Nvveen/Gotty@v0.0.0-20170406111628-a8b993ba6abd>: unknown revision a8b993ba6abd
go: error loading module requirements
green-morning-1318
05/13/2019, 9:35 PMreplace <http://github.com/Nvveen/Gotty|github.com/Nvveen/Gotty> => <http://github.com/ijc25/Gotty|github.com/ijc25/Gotty> v0.0.0-20170406111628-a8b993ba6abd
to your go.mod
filegreen-morning-1318
05/13/2019, 9:36 PMwide-judge-30323
05/14/2019, 1:29 AMbucket.onObjectCreated
and bucket.onObjectRemoved
.
If I have multiple events defined (which is perfectly valid in s3), removing 1 removes them ALL. Is this a known bug?dazzling-scientist-80826
05/14/2019, 9:03 PMThe Pulumi runtime detected that 114 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
It definitely is the second case: a cyclic dependency, but I’m not sure how to break the cycle. I’ve got a lambda that closes over a function that constructs a config/context object sort of thing, but another lambda that needs the arn of that first lambda - is there some general trick to break the cycle in this sort of situation?orange-tailor-85423
05/14/2019, 9:55 PMorange-tailor-85423
05/14/2019, 9:56 PMstocky-spoon-28903
05/14/2019, 9:57 PMorange-tailor-85423
05/14/2019, 9:58 PMorange-tailor-85423
05/14/2019, 11:00 PMorange-tailor-85423
05/14/2019, 11:00 PMstocky-spoon-28903
05/14/2019, 11:03 PM