damp-holiday-59303
03/16/2022, 3:21 PMpulumi up
and pulumi refresh
to stop working. So I exported the stack, edited the JSON to remove all references to resources or providers in the removed account, and imported the stack.
Now, pulumi refresh
works fine, and the stack looks right in the UI and when I export it and look at the JSON. But when I try to run pulumi up
it still complains because it tries to assume a role in the old account to refresh a resource that no longer exists in the stack. The resource referred to in the error message is not present in the UI, using pulumi stack --show-urns
or when exporting and grepping the stack.json.
How can this be? Why is Pulumi still trying to access that resource that it shouldn’t even know exists at this point?echoing-dinner-19531
03/16/2022, 3:24 PMpulumi preview
also error due to the role change?damp-holiday-59303
03/16/2022, 3:26 PMpulumi preview
fails as well.getOrganization().accounts
and trying to create a new resource in the deactivated account.echoing-dinner-19531
03/16/2022, 3:35 PM