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

Yes, you can do this. Or you can use any other configuration technology; your preferred language may have a better way of sharing configuration "above" stack level.
If you want to use Pulumi's provided configuration features, you wouldn't use `pulumi.Output()` specifically (though that would be used in the implementation). You would use a separate project, probably with only one stack (or at least, very few). And you would get shared configuration from that project/stack through stack references.

Note we do have plans to extend project config to also support global config: <https://github.com/pulumi/pulumi/issues/11550>

Excellent thank you both for the input. For the time being, I was going to do the meta-project approach that you mentioned <@U012UJTT55M> (I think that's how I originally was trying to explain this so we both are thinking the same thing). This meta-project would just have a single stack that defines a bunch of namespaced config, that just does a bunch of `pulumi.export()` on.

This could be a simple stop-gap until global configuration becomes a thing as Fraser mentioned and shouldn't be too hard for me to switch away from.