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

_creating thread to avoid taking up too much space in main chat_

the migration scripts would be much easier to manage if I could store some kind of version number in the micro-stack's state to indicate which version of the deployment script the state represents, this will help me understand which migration steps need to be run for the micro-stack

is there any way to do this? I did think maybe I could just export `deployment_script_version` as a static string updated each time I need to bump, but I wasn't entirely sure if there isn't already an existing mechanism in place. thank you :pray:

Yes, exporting is good for this. You can also export it as `readme` and it'll be displayed nicely in the Pulumi console