fancy-spoon-7206
08/24/2022, 1:23 PMpulumi up
would do the trick. I did not add any code to set the config.
Now with the automation API all I see in the examples is
// set stack configuration specifying the AWS region to deploy
s.SetConfig(ctx, "aws:region", auto.ConfigValue{Value: "us-west-2"})
Is there a way to consume config using a Pulumi.dev.yaml
file? instead of setting one config at a time.
Pulumi.dev.yaml
config:
aws:region: us-east-2
aws:profile: sandbox
aep:config:
bucket:
name: dinesh-test
limited-rainbow-51650
08/24/2022, 2:47 PMPulumi.dev.yaml
file will be automatically read when dev
is your active stack. The calls you see in the code are configuration settings which will be overlayed on top of what is in the file. This gives you the option to have some values committed to source control and to add (or overwrite) some values which come from somewhere else.fancy-spoon-7206
08/24/2022, 3:15 PMConfig:map[string]string(nil)
. That makes me believe <http://Pulumi.dev|Pulumi.dev>.yaml
is not being read as a part of the context. Is the behavior you are talking about different from normal Pulumi programs than automation API programs?proud-machine-85126
08/31/2022, 4:01 AM