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

No. If you could do that, then your stack would not represent what Pulumi thinks is in the provider / cloud, it would represent what is in your code. The purpose of the stack is to allow Pulumi to figure out the minimal changes it needs to perform in order to make the provider look like the code.

If you had, for example, a config value that was used as the target number of instances in an auto-scaling group, and you updated that in the stack but not the provider, then when you next ran `up`, Pulumi would not know to change the provider. So your target number of instance would remain wrong forever.