This message was deleted.

sparse-intern-71089

03/23/2021, 11:50 AM

This message was deleted.

✅ 1

👍 1

gentle-diamond-70147

03/23/2021, 4:08 PM

Do you have custom

aws:

configuration values in your stack configuration? I believe this can occur when you've set "custom" configuration values under the

aws:

namespace which is reserved for the default provider itself.

👍 1

gentle-diamond-70147

03/23/2021, 4:12 PM

In other words, if you were to do

pulumi set aws:myCustomConfig asdf

, you would get that error message because

myCustomConfig

is not a valid configuration property on the

aws.Provider

👍 1

microscopic-agent-70604

03/23/2021, 4:29 PM

Yes. We did it like this. We have aws: namespace and put there every our configuration parameter. Do you have a link or some document where it's written that we can't do it or some architecture link?

gentle-diamond-70147

03/23/2021, 4:42 PM

Our general config documentation is at https://www.pulumi.com/docs/intro/concepts/config/#configuration-keys, but I'm not sure if we explicitly explain it in those terms.

👍 1

gentle-diamond-70147

03/23/2021, 4:42 PM

For your own custom configuration you can just use

pulumi config set myCustomConfig asdf

without the

aws:

prefix and use the configuration values that way.

👍 1

14 Views

Open in Slack

Previous Next

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.