rhythmic-finland-36256
09/04/2019, 4:20 PMmyproject:baseurl
? My question is about simple programs, not higher-level constructs or providers. Is it even better to use top-level configs to avoid overlapping with third party libs / providers?white-balloon-205
pulumi config set baseurl value
or with pulumi config set myproject:baseurl value
).
Namespaces are primarily designed for reusable libraries (like aws
or cloud
).
Once we support structured config (maps and lists), then you will be able to have more hierarchichcal configuration without the need for separating top level config namespaces.rhythmic-finland-36256
09/04/2019, 4:29 PMaws
. From CLI perspective both look the same (replace myproject
by aws
).white-balloon-205
luke:~/dd/pulumidemos/myproject
$ pulumi config
KEY VALUE
aws:region us-east-1
luke:~/dd/pulumidemos/myproject
$ pulumi config set baseurl value
luke:~/dd/pulumidemos/myproject
$ pulumi config
KEY VALUE
aws:region us-east-1
baseurl value
luke:~/dd/pulumidemos/myproject
$ pulumi config set myproject:baseurl2 value2
luke:~/dd/pulumidemos/myproject
$ pulumi config
KEY VALUE
aws:region us-east-1
baseurl value
baseurl2 value2
rhythmic-finland-36256
09/04/2019, 4:39 PMmyproject
was a bit misleading. This basically means it doesn’t matter if I provide therealprojectname:
as prefix as this is used if the key is not namespaced. If I use someotherprefix:
this will create a different namespace which is technically the same as aws
?aws
would not be the best idea 🙂white-balloon-205
So I’ll stick to non-namespaced keys for now.Yes - that's generally recommended for application config.
This also means calling my pulumi projectIndeed - that's the core flaw of this approach unfortunately.would not be the best idea 🙂aws
rhythmic-finland-36256
09/04/2019, 4:58 PM