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

Maybe you could utilize the argument of the `pulumi up` command:
```--config-file string```
And provide the path to the config file containing the large amount of config values?

I don't know if there are other options, but did you know that stack outputs can also be objects including multiple properties. This way you don't need one output per "global" config value but you can create one output which holds all "global" values.

those are both very good ideas, will try them out

If you're orchestrating multiple stacks, it may be easier to manage (including shared config) if you wrap them with automation api. <https://github.com/pulumi/pulumi/issues/3901>

<@UQ8K13T7X> yeah I will definitely look at that, but I'm waiting for C# version

looks like using the --config-file command doesn't work as it uses that to determine the state file, so if you try and use the same config for two projects the second try's to delete the content of the first