This message was deleted.

In general we recommend putting all project config in the default namespace (available with just

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.

I don’t get the difference between default namespace with a colon-based key to using a namespace like

aws

. From CLI perspective both look the same (replace

myproject

by

aws

).

Not sure I'm following the latest points. Leaving off the namespace defaults to using the project name as the namespace. The CLI normalizes this down to the simpler form when listing config:

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

Understand. I currently didn’t use the same term for the prefix and the project name, so

myproject

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

?

So I’ll stick to non-namespaced keys for now.

Yes - that's generally recommended for application config.

This also means calling my pulumi project

aws

would not be the best idea 🙂

Indeed - that's the core flaw of this approach unfortunately.

All right. Understood. Thanks a lot for clarifying!