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

Ah...just found these:
<https://github.com/pulumi/pulumi/issues/6719>
<https://github.com/pulumi/pulumi/issues/2307>

Can I ask why you might want to lock a particular profile in for an entire project? The easiest way to manually test Pulumi code is to switch profile to a test account and `up`..

we have a profile that has some shared resources among users, due to the deployment environment. It's weird, for sure. Typically you'd want that profile to be associated with a particular user and limit based on that, however, we are using a profile that allows deployments for multiple cloud admins

It would still be helpful to have hierarchal configs where there is a default value for many values for multiple stack configs that doesn't have to be rewritten over and over

Yep. Well, for now the solution is language-specific.

do you have a link in mind for samples on how to do that?....I was trying to read in different StackReferences however, I wasn't really able to properly get/merge a config with the existing stack...