Any advice on escaping “.” In the config set command? We’d like to end up with foo.bar.bar2.bar3: secure: encryptedval But we end up getting this when we use “.” anywhere in the passed in value foo: bar: bar2: bar3: secure: encryptedval

you’re getting this even when you don’t pass the

--path

flag?

—path worked but our new issue is now the engineer that needs to run it will likely use power shell and power shell gets angry when we use bracket notation so for example pulumi config set-all --path --plaintext '["parent.name"].["nested.name"]'=value doesn’t work for use in power shell

Ah, I was answering the question about escaping the

.

- it sounds like you’re now asking about the reverse… i.e. setting a nested value within an object - is that right?

Yeah we want a nested value inside an object Like example config:foo: Bar: value1 Bar2: value2 Bar3: value3

hmm… try

pulumi config set "parent.name" "{\"nested.name\": \"value\"}"

The end result for the last one was Config😛arent: name: ‘{nested.name: value}’ With the —path flag on

Yeah… don’t use the path flag

Without —path results with Config😛arent.name: ‘{nested.name: value}’

Isn’t that what you want?

Is that functionally the same as config:foo: Bar: value1 Bar2: value2 Bar3: value3 Maybe I’m misunderstanding. These will be secrets too so ultimately it will be secure values inside too.