little-river-49422
02/06/2019, 2:51 PMwhite-balloon-205
02/06/2019, 4:44 PMlet config = new pulumi.Config()
let thing = config.get("thing") || "defaultThing";
little-river-49422
02/06/2019, 4:52 PMwhite-balloon-205
02/06/2019, 4:56 PMlittle-river-49422
02/06/2019, 5:01 PMwhite-balloon-205
02/06/2019, 5:01 PMpulumi new
) functionality - which drives the prompts you see during a pulumi new
operation. This is slightly more clear if you expand the screenshot a little - but definitely understand the confusion. We do expect to make some improvements generally around config in the not-too-distant future - see https://github.com/pulumi/pulumi/issues/1052.little-river-49422
02/06/2019, 5:05 PMwhite-balloon-205
02/06/2019, 5:16 PMPulumi.yaml
is not used for configuration.
The current configuration values are stored in Pulumi.<stackname>.yaml
(confusing that these have similar names - the two files are completely unrelated).
Defaults and how the config is used/interpreted is entirely up to the program.
Note that this is related to the use of "code" vs. "configuration DSLs" - we lean on the code to do as much of the work as possible.little-river-49422
02/06/2019, 6:11 PMwhite-balloon-205
02/06/2019, 6:27 PMtemplate
section which is used when templates are installed via pulumi new
, or via New Project
in the Pulumi console.