This message was deleted.

sparse-intern-71089

11/28/2021, 9:09 PM

This message was deleted.

little-cartoon-10569

11/28/2021, 9:11 PM

You create a config instance per prefix.

Copy code

const location = new pulumi.Config('azure-native").require("location");

orange-kite-80991

11/28/2021, 9:28 PM

thx!

orange-kite-80991

11/28/2021, 9:28 PM

A sample like that could be added to the Pulumi Config wiki page.

little-cartoon-10569

11/28/2021, 9:57 PM

Yes, it's only in there as a few sentences, and in a specific context that does not seem to apply (but actually does):

If you are writing code that will be imported into a broader project, such as your own library of components, you should pass your library’s name to the constructor. This string is used as a namespace for all configuration keys. Similarly, if you want to access the config of another library, such as the config for a standard library like aws, you should also pass the library’s name to the constructor.

orange-kite-80991

11/28/2021, 11:18 PM

Ah. It's a Typescript-ism. Unfortunately I'm a Python programmer coming into a Typescript+Pulumi project. Never sure which patterns might be standards from one or the other language.

orange-kite-80991

11/28/2021, 11:31 PM

I know what namespacing looks like in Python but not so much in TS.

little-cartoon-10569

11/28/2021, 11:33 PM

This isn't TS namespacing, it's specific to pulumi.Config's implementation.

little-cartoon-10569

11/28/2021, 11:35 PM

Which is why I say that this is a specific context (a library has a namespace). But in fact there's no need for it to be a library: if you want configuration for your firewall and for your ACLs in the same config file, you can add a call to

new pulumi.Config('acl')

and

new pulumi.Config('firewall')

, and it'll get values from those namespaces. Nothing to do with libraries...

little-cartoon-10569

11/28/2021, 11:35 PM

The docs are unnecessarily-specific.

orange-kite-80991

11/28/2021, 11:43 PM

Thanks. And I recognize the challenge of maintaining language generic documentation while also trying to support language & context specific queries from newbies like me. Always appreciate your help.

👍 1

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.