cloudtools/stacker

handle multiple users updating a stack at once

Open

#65 opened on Aug 10, 2015

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (166 forks)batch import
enhancementhelp wantedquestion

Repository metrics

Stars
 (706 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Right now there's no special logic that would stop 2 people from attempting to update stacks at the same time. In general the second attempt will see the stacks being updated, and probably do the right thing, but I can see some cases where that wouldn't happen and could leave stacks in invalid states.

So - probably worth having some way to lock the stack while you're working on it. Not sure where that would be handled.

Contributor guide

Research direction
Investigate how stacker currently handles stack updates and identify where a lock mechanism could be implemented. Look for existing locking patterns in the codebase or propose a simple mutex per stack. Consider using a distributed lock if multiple processes can run.
Tech stack
python
Domain
clouddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70