What happened?
Unfortunately there was (/is) a major identity issue in OCI which makes a lot of requests to end up with 404 errors.
In OCI there's no special error code for not authorized, and it's 404 not authorized or not found. That means, permission issues are handled the same as not found.
This leads to deletion of resources from state, then when no more permission issues, we get "already exists" errors.
Steps to reproduce
Create some resource, remove permissions, exec pulumi couple of times, fix permissions and get already exists error.
Expected Behavior
Reuse the existing resource
Actual Behavior
Resources are deleted from state
Output of pulumi about
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
What happened?
Unfortunately there was (/is) a major identity issue in OCI which makes a lot of requests to end up with 404 errors.
In OCI there's no special error code for not authorized, and it's 404 not authorized or not found. That means, permission issues are handled the same as not found.
This leads to deletion of resources from state, then when no more permission issues, we get "already exists" errors.
Steps to reproduce
Create some resource, remove permissions, exec pulumi couple of times, fix permissions and get already exists error.
Expected Behavior
Reuse the existing resource
Actual Behavior
Resources are deleted from state
Output of
pulumi aboutNo response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).