https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
f
I believe you can use 
--path
for this, like so:
Copy code
pulumi config set --path namespace.key
b
I thought so maybe, but it does not; 
pulumi config set --path winnie.twingate.name jolly-porpoise
creates this:
Copy code
aws:winnie:
  twingate:
    name: jolly-porpoise
(that is, it just nests it underneath)
f
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
b
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 🙂
f
TIL! I must have glossed over that part when I was reading the docs
b
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
✅ 1
f
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
I don't know if that'd work with 
--path
, but I'd try 
pulumi config set --path 'winnie:twingate.name'
b
ah! you're right, that works
thank you - sometimes you just need an extra set of eyes
f
Happy to help 😄
10 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by