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

we use this NPM Package for Environment configs within Pulumi
<https://www.npmjs.com/package/config>

And the more specific implementation of it is managed by setting a pulumi config variable on the stack which is used by the NPM Config package referenced here: <https://github.com/lorenwest/node-config/wiki/Environment-Variables#node_config_env>

<@UKV77NZJT> you must import your k8s resources from somewhere in your application. They will not automatically be picked up in sub-directories.

Also, you must use an exported object otherwise Node will "optimize" it away as unused. This is explained in more detail at <https://www.typescriptlang.org/docs/handbook/modules.html#optional-module-loading-and-other-advanced-loading-scenarios>.

thanks, did not know about the unused optimization. exporting the resources fixes the issue

It confused me at first too. :slightly_smiling_face: