gorgeous-minister-41131
07/20/2021, 8:32 PMerror: unexpected duplicate resource 'urn:pulumi:test::aws-eks-py::aws:iam/role:Role$aws:iam/rolePolicyAttachment:RolePolicyAttachment::test-arn:aws:iam'
faint-table-42725
07/20/2021, 9:01 PMpulumi stack rename
along the lines of error: [409] Conflict: A stack named projectname/stackname already exists
gorgeous-minister-41131
07/20/2021, 9:10 PMtest
and I renamed test-v2
-> test after previously removing the test
stack from the same project.test
lying around on the app’s filestoretest-v2
got obliterated from the UI and the usable CI aftter performing the rename, so I can’t even force re-import a version of test-v2
state back in even if I wanted tofaint-table-42725
07/20/2021, 9:24 PMtest
stack, which you deleted. Then, you had a new stack called test-v2
which you then renamed to test
and then bad things happened?gorgeous-minister-41131
07/20/2021, 9:27 PMerror: unexpected duplicate resource 'urn:pulumi:test::aws-eks-py::aws:iam/role:Role$aws:iam/rolePolicyAttachment:RolePolicyAttachment::test-arn:aws:iam'
I know that’s the case since the old deleted stack was about 1 month older than the test-v2 stack (which I renamed to test) and I recognized the duplicated resources.faint-table-42725
07/20/2021, 9:29 PMgorgeous-minister-41131
07/20/2021, 9:29 PMfaint-table-42725
07/20/2021, 9:30 PMgorgeous-minister-41131
07/20/2021, 9:30 PMaws:iam:RolePolicyAttachmet
aws:iam:RolePolicyAttachment
faint-table-42725
07/20/2021, 9:32 PMgorgeous-minister-41131
07/20/2021, 9:32 PMpulumi export
before I rename any stacks on app.puluim.com just so I have a copy in case 😉faint-table-42725
07/20/2021, 9:45 PMgorgeous-minister-41131
07/20/2021, 9:46 PMfaint-table-42725
07/20/2021, 9:46 PMgorgeous-minister-41131
07/20/2021, 9:47 PMpulumi stack rm
do the same.faint-table-42725
07/20/2021, 9:54 PMgorgeous-minister-41131
07/20/2021, 9:55 PM