coreos / coreos/coreos-assembler
`remote-prune` should query EC2 for AMIs
Open
Nobody has claimed this yet.
jira
- Dominant language
- Go
- Stars
- 393
- Forks
- 193
- Avg merge
- 17h 6m
- Merged PRs (30d)
- 5
Description
Instead of relying on AMIs listed in the build metadata, we should query EC2 directly for the list of AMIs and cross-check. That way, if we're interrupted or they're desynchronized somehow, we don't leak images.
(Taken from @jlebon's comment https://github.com/coreos/coreos-assembler/pull/839#issuecomment-548556519)
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 at the remote-prune entry point and trace how it currently obtains AMIs from build metadata. Review the EC2 query and cross-check requirements, then verify that interrupted or desynchronized runs do not leave images behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100