rhythmic-finland-3625609/04/2019, 4:20 PM
? 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?
pulumi config set baseurl value
). Namespaces are primarily designed for reusable libraries (like
pulumi config set myproject:baseurl value
). 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-3625609/04/2019, 4:29 PM
. From CLI perspective both look the same (replace
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-3625609/04/2019, 4:39 PM
was a bit misleading. This basically means it doesn’t matter if I provide
as prefix as this is used if the key is not namespaced. If I use
this will create a different namespace which is technically the same as
would not be the best idea 🙂
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 🙂
rhythmic-finland-3625609/04/2019, 4:58 PM