Replies: 2 comments
-
@prudnikov Thanks for the question! |
Beta Was this translation helpful? Give feedback.
-
@abhinav Thanks for the answer. Just to make sure migration path is clear to me (and hopefully to anyone who will be on the same migration process) imagine the following situation: We migrate to the new naming format with Now I can rename stack |
Beta Was this translation helpful? Give feedback.
-
In Pulumi v3.61.0 state scoping was changed. I'd like to migrate project by project to the new structure just not to have long stack names.
We use a custom S3 backend for the pulumi state. We have lots of projects with lots of environments each.
Documentation states:
I expect that
pulumi state upgrade
should be executed inside one of the projects, and state scoping will change only for the current project, but this is still unclear to me. Can you please confirm that my expectation is correct? Or will it update scoping for all projects in the organization?Beta Was this translation helpful? Give feedback.
All reactions