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

Can you elaborate a bit? I'm not following.

I have two stacks: xxxx/preprod/network and xxxx/prod/network, the module that supplies those stacks saves config parameters locally in a pulumi.network.yaml file so if I work on preprod then stack select the prod module unless I call pulumi config refresh it freaks out and tries to destroy everything because the configuration variables differ

So your module has instituted it's own configuration system, am I understanding that right?

Otherwise the config files would be `Pulumi.preprod.yaml` and `Pulumi.prod.yaml`

no, I believe the config file takes on the final stack name, since mine is 3 deep it's taking on network