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.

Pulumi Community

Nope. That's one of the many advantages of using a general-purpose language :slightly_smiling_face:

Though it's probably a good idea not to use those alternative sources in ComponentResources or similar. That becomes a "sneaky" dependency, making it harder to get the configuration just right when moving to other machines or getting other people to run deployments. Having all the variables in source control, right beside your code, is pretty handy.

But if you use them directly in your index.ts or similar, then it's pretty easy to ready the code and resolve those sorts of issues.

Ahh gotcha, that makes sense. Appreciate the answer :pray:

Despite best practices, team is small and tends to just zip up the `.env` files + share so they're usually in source with rest of code.

For some things I think I need to keep it in the stack YAML though for sure