fancy-fall-81083
09/19/2018, 3:43 PMfancy-fall-81083
09/19/2018, 3:55 PMstocky-spoon-28903
09/19/2018, 4:04 PMfancy-fall-81083
09/19/2018, 5:48 PMfancy-fall-81083
09/19/2018, 7:49 PMconst resourceGroup = await azure.core.getResourceGroup …
) but am stuck in reading about the typescript Promise type and brain compiling to javascript. Any hints would be highly appreciated. As I am new to async/await that might be my main problem. @stocky-spoon-28903’s example seems to be just the core and I am just not getting how to do my async/await call so that nodejs does not fail with an ReferenceError: resourceGroup is not defined
when using resourceGroup.name
later in the code.billowy-army-68599
glamorous-printer-66548
09/19/2018, 11:16 PMglamorous-printer-66548
09/19/2018, 11:16 PMnamespace
to child components in k8s.creamy-potato-29402
09/20/2018, 2:05 AMglamorous-printer-66548
09/20/2018, 2:28 AMpulumi destroy
it seems to run the deletion sequentially for each single resource and it is therefore really slow. Is this intentional / known?creamy-potato-29402
09/20/2018, 5:40 AMcreamy-potato-29402
09/20/2018, 5:42 AMcreamy-potato-29402
09/20/2018, 5:42 AMwhite-balloon-205
helpful-vegetable-35581
09/20/2018, 7:07 AMhelpful-vegetable-35581
09/20/2018, 7:08 AMglamorous-printer-66548
09/20/2018, 7:32 AMcuddly-monkey-57285
09/20/2018, 2:12 PMaloof-tailor-93191
09/20/2018, 9:05 PMchilly-pharmacist-32380
09/20/2018, 9:43 PMwooden-toddler-96888
09/20/2018, 11:46 PMerror: could not find plugin for provider 'urn:pulumi:pulumi-stack-polyverse-dot-com::aws-ts-eks::pulumi:providers:aws::default'
glamorous-printer-66548
09/21/2018, 12:33 AMinfra
subdirectory. However It’d like to keep the Pulumi.yaml
in the repo root to be able to run pulumi CLI commands in the repo root. However it seems pulumi assumes the package.json to be in the same directory as the Pulumi.yaml and if that’s not the case it crashes with a bunch of errors.
Is there a way to specify in the Pulumi.yaml a custom location of the package.json? Also is there some general docs / schema reference for the Pulumi.yaml ?glamorous-printer-66548
09/21/2018, 5:13 AMkubectl apply
of k8s manifests that’s possible.
Thoughts?fresh-flag-12765
09/21/2018, 1:56 PMerror: expected string or JSON map; got resource.Computed
. The issue appears to be lines 118-121 where I am trying to use the outputs of two resources to create a new policy. The getBucketPolicy
function thus would be the issue.
(If I comment out the bit creating the policy the rest of it seems fine)fresh-flag-12765
09/21/2018, 2:17 PMfresh-flag-12765
09/21/2018, 2:28 PMbright-motherboard-93404
09/21/2018, 5:56 PMuser_data
that I'm supplying to my ec2 instances isn't getting run. When I log in with ssh and run the same command (python -m SimpleHTTPServer), everything works as expected. Is there any way to debug this situation?billowy-army-68599
~/pulumi/bin/pulumi-resource-aws
Does each provider (ie, gcp for example) create these? I can't find them installed on my system anywhere, so not sure how it works. Does pulumi itself shell out to these providers in some way?dazzling-scientist-80826
09/21/2018, 9:32 PMfull-dress-10026
09/21/2018, 10:24 PMcloud.Service
and I received this message after running pulumi update
for the first time:
error: Plan apply failed: 1 error occurred:
* creating urn:pulumi:basic-web-container-dev::basic-web-container::cloud:service:Service$aws:ecs/service:Service::basic-web: timeout while waiting for state to become 'true' (last state: 'false', timeout: 10m0s)