IAM Policy for `ptd-controller` Failing to Delete in Persistent Step
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Summary
The IAM Policy for ptd-controller fails to delete during the persistent step, blocking the destruction workflow.
Context
During the teardown process, the IAM policy deletion fails, likely due to dependencies on resources that will be cleaned up in subsequent steps.
Details
- Affected Resource: IAM Policy for
ptd-controller - Step:
persistent - Operation: Delete
- Dependency Issue: Policy appears to be tied to resources that exist in later cleanup steps
Current Understanding
- The policy deletion is blocked by active attachments or dependencies
- These dependencies are cleaned up in following steps of the teardown process; maybe this is a one-off and no action is needed here?
Notes
The ptd-controller infrastructure may be going away, which could make this a temporary issue worth working around rather than fixing comprehensively.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the teardown workflow's persistent step and the IAM policy's active attachments or dependencies. Done means establishing whether deletion needs a change or whether the failure is a one-off that should only be worked around.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100