concourse / concourse/pool-resource
pool-resource needs an atomic move operation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Moved from concourse/concourse#196
cc @xtreme-gavin-enns
Currently in order to move an environment between pools (to model state changes) we need to perform separate add and remove operations. This has two downfalls:
- one operation may fail leaving us with duplicated or deleted environments
- one operation may take a long time, leaving us temporarily in a state similar to the above
This could be resolved by implementing a move operation that performs both parts of the move in a single commit/push.
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 locating the existing add and remove operations for moving environments between pools. No file or test is named, so trace how those operations commit and push state, then verify that a move performs both changes in one commit/push without leaving duplicated or deleted environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100