Page MenuHomePhabricator

Scap3 should have idempotent deploys
Closed, ResolvedPublic2 Story Points


Scap3 currently follows the trebuchet model of tagging a revision and ssh-ing to machines to check out that tag, regardless of whether that tag represents an actual code change. Scap3, currently, then runs service restarts and port checks. Ideally it should not make changes to services, or run checks, if code doesn't change.

Event Timeline

thcipriani updated the task description. (Show Details)
thcipriani raised the priority of this task from to Needs Triage.
thcipriani added a project: Deployments.
thcipriani added subscribers: mmodell, demon, dduvall and 3 others.

True idempotent behavior is fairly difficult to pull off. We can either half-ass it or we can use something like puppet for the bulk of our deployment logic.

I'm not the biggest puppet fan but I recognize that what this task is subtly proposing is to reinvent that wheel and I'm not sure we are ready to open that can of worms.

^ bad metaphor overload.

mmodell set Security to None.Oct 12 2015, 4:16 PM
mmodell edited a custom field.
dduvall triaged this task as Normal priority.
dduvall moved this task from Needs triage to Services MVP on the Scap board.
dduvall closed this task as Resolved.Oct 30 2015, 6:54 PM
dduvall moved this task from Services MVP to Done on the Scap board.