full-dress-1002609/27/2018, 11:04 PM
full-dress-1002609/28/2018, 1:35 AM
full-dress-1002609/28/2018, 4:00 AM
is documented as
. What does
-c, --config stringArray
mean when called from the command line?
And it actually updated my stack config file to contain
pulumi update --config 'cloud-aws:externalVpcId=asd'
. I was expecting that it was merge in my CLI config options in memory and not actually update the config file.
. Curious to understand the scenario that motivates you to want to set configuration on the update but not persist it? How will you know what to do for the next update?
full-dress-1002609/28/2018, 4:15 AM
with a VPC created in code and the only way to configure that is via the config file. My plan was to create all my other infrastructure in project1, mark all the required
config params as exports, and use them to
the project, project2, that contains my
. Because the resources in project2 depend on project1, project2 cannot and should not be deployed without project1 being deployed. As a side note: I expected the
flag to do the merge in memory rather than mutate the file because if I wanted a file mutation I would've just used
being a little surprising makes sense too.
pulumi update —config
prior to constructing any resources from cloud that depend on the network, you can override this in code. I recall working with a user who was doing this a couple months ago. (This is exactly what we want to support in a more first class way as part of https://github.com/pulumi/pulumi-cloud/issues/601)
full-dress-1002609/28/2018, 4:33 AM
params prior to constructing the resources that require the network?
does not have any implicit dependencies on values from other resources, I believe I need to add some resources to the
list, assuming that does what I expect 🙂
was created in the default-vpc that Pulumi created.