https://pulumi.com
Join Slack
what am I missing here as far as downstream impact?
# general
c
what am I missing here as far as downstream impact?
l
To test, you could run 
pulumi stack export
to json, then 
pulumi stack import
the same file. If that works, then you could run the upgrade, and if you don't like what you find, then you at least know you can import the original stack.
e
as long as your on a recent CLI version and no one is trying to use these stacks with like a CLI from 2023 there shouldn't be any impact
c
having import issues now - this is moving between stacks. Keeps saying this is not from the same stack (of course it isn't, that's why I want to move it)
e
That sounds like a different problem? Is that trying to export a stack from one name and import it under another name? I don't think import will handle that directly, you have to edit the file to fix up all the names.
c
had to do manual surgery
really disincentivizes assigning/building infra per repo/app.
Teams changes, people get tired of names, repos get deprecated etc.
e
So this is moving a resource from one stack to another? Did you see 
pulumi state move
, if you did why didn't that work out?
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by