early-musician-41645
03/06/2019, 10:26 PMv0.17.0
but I'm seeing this error on `npm install`:
]$ npm install
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @pulumi/eks@0.17.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'eks-cluster'
npm ERR! notarget
helpful-advantage-49286
03/06/2019, 11:38 PMhelpful-advantage-49286
03/06/2019, 11:38 PMhelpful-advantage-49286
03/06/2019, 11:38 PMglamorous-printer-66548
03/07/2019, 2:36 AMlemon-spoon-91807
03/07/2019, 8:00 AM0.17.1
version of `@pulumi/pulumi. This change brings two nice improvements (which we will also document and blog about soon).lemon-spoon-91807
03/07/2019, 8:01 AMComponentResource
will now end up causing you dependOn all the child resources of that ComponentResource
. This is useful when a component represents an aggregation of many real resources, and you don't want some dependent resource to be created until that entire aggregation finishes being created.lemon-spoon-91807
03/07/2019, 8:03 AMOutput
wrapping that object. i.e. instead of neeing to write code like:
certificate.domainValidationOptions.apply(d => d[0].resourceRecordName) // you can now just write
certificate.domainValidationOptions[0].resourceRecordName
lemon-spoon-91807
03/07/2019, 8:03 AMlemon-spoon-91807
03/07/2019, 8:04 AM@pulumi/pulumi
package are of the sort that will not necessarily play well if prior versions of that same package are loaded into an app. For example, if you reference this new 0.17.x
version of @pulumi/pulumi
it won't necessarily work properly if you have a library that ends up pulling in an 0.16.x
version. This is because hte 0.16.x version won't properly keep track of things like the component-dependencies. Nor will it properly allow you to lift those members. Because of the problems and confusion this could cause, we have updated pulumi
to warn if you run an app that mixes/matches across these versions.lemon-spoon-91807
03/07/2019, 8:07 AM@pulumi/...
packages so that they refer to @pulumi/pulumi
v0.17.x. If you'd like to try any of this out, please go ahead and let us know if you run into any problems. We tried to extensively test these changes across every library and use case we have ourselves. But it might be the case that we missed something that occurs in the wild.lemon-spoon-91807
03/07/2019, 8:08 AMmillions-judge-24978
03/07/2019, 3:30 PMnew aws.ec2.NatGateway
, receiving the error:
error: aws:ec2/natGateway:NatGateway resource 'us-east-1c' has a problem: "allocation_id": required field is not set
I am providing to the input allocationId
, a pulumi.Output<string>
that is coming directly from a `new aws.ec2.Eip`'s allocationId
output.
I can't tell if this is a pulumi issue or not.important-leather-28796
03/07/2019, 9:21 PMalert-fish-36749
03/07/2019, 9:43 PMpulumi init
to set up a gcp-typescript example dir, then deleted ~/.pulumi
(using local store). Now when I try to pulumi up
after logging back into the local store, I get a plugin failure:alert-fish-36749
03/07/2019, 9:44 PMalert-fish-36749
03/07/2019, 9:44 PMquaint-queen-45003
03/07/2019, 9:53 PMalert-fish-36749
03/07/2019, 10:03 PMpulumi up
just blindly applied the recorded state diff (and then fails because some things exist already). Am I right that there's no way to read the true state of prod into a pulumi state and pick up from there?alert-fish-36749
03/07/2019, 10:07 PMfaint-vegetable-61837
03/07/2019, 10:07 PMhallowed-king-98702
03/07/2019, 10:50 PMfresh-chef-62390
03/08/2019, 12:55 AM$ pulumi stack ls
NAME LAST UPDATE RESOURCE COUNT
demo-dev* 2 weeks ago 2
$ pulumi stack rm demo-dev
This will permanently remove the 'demo-dev' stack!
Please confirm that this is what you'd like to do by typing ("demo-dev"): demo-dev
error: 'demo-dev' still has resources; removal rejected; pass --force to override
better-rainbow-14549
03/08/2019, 9:27 AMsticky-bear-14421
03/08/2019, 1:12 PM: RUN curl -fsSL <https://get.pulumi.com> | sh
---> Running in a5a1a92cdca4
=== Installing Pulumi v0.16.16 ===
Whereas homebrew updated to 0.17.1 a few days ago. You forgot to update the release in the https://pulumi.io/latest-version link.sticky-bear-14421
03/08/2019, 1:16 PMbetter-rainbow-14549
03/08/2019, 2:05 PMsticky-bear-14421
03/08/2019, 2:09 PMsticky-bear-14421
03/08/2019, 2:16 PM<https://get.pulumi.com/releases/sdk/pulumi-v${VERSION}-${OS}-x64.tar.gz>
better-rainbow-14549
03/08/2019, 2:19 PM