This message was deleted.

I believe you can use

--path

for this, like so:

pulumi config set --path namespace.key

I thought so maybe, but it does not;

pulumi config set --path winnie.twingate.name jolly-porpoise

creates this:

aws:winnie:
  twingate:
    name: jolly-porpoise

Oh, I think I see what you're saying. I'm not aware of the existence of

namespace

as a concept in Pulumi configs; I'm under the impression that the top-most level of config directives are the Pulumi project name

they talk about it a little here: https://www.pulumi.com/docs/intro/concepts/config/#code Basically you pass in a parameter to

pulumi.Config()

and that separates out everything. I learned that if you set random things in the

aws

namespace, the aws provider tries to validate them against its own rules and then throws an error 🙂

TIL! I must have glossed over that part when I was reading the docs

it could be that I should go through the process of renaming (can I do that? it might be recreating) the project now that I understand the project naming better, to save myself future trouble

Looking closer at the doc you linked, it seems like you can create a new namespace by doing a

pulumi config set <new namespace>:aKey

ah! you're right, that works

Happy to help 😄