deployment-patterns

Files (2)

• SKILL.md
• SKILL.md.lock

SKILL.md (first lines)

<!-- bodyRef: skills/sources/deployment-patterns.md -->

<!-- Generated by `harness skills bootstrap`. Edit to tune; re-run to regenerate. -->
<!-- Static skills point at live docs by design — do not hardwire version-pinned API here. -->

Use this skill when shipping, releasing, or reviewing deploy configuration.

## Concepts (timeless)
- Build once, promote the same artifact across environments; configuration comes from the environment, not the build.
- Make releases reversible: keep the previous version deployable and have a rehearsed rollback.
- Roll out progressively (canary/blue-green) for risky changes; watch health signals before full cutover.
- Migrations are forward-compatible and reversible; decouple schema changes from code that requires them.
- Health checks, readiness gates, and observability are part of "done", not follow-ups.

## Pull current docs first
Platform + orchestration APIs change frequently — confirm the current docs for THIS target:
- your deploy platform + orchestrator's current docs

## Checklist
- [ ] Immutable artifact promoted across envs; config externalized
- [ ] Rollback path exists and is rehearsed
- [ ] Risky changes rolled out progressively with health gates
- [ ] Migrations forward-compatible + reversible
- [ ] Health/readiness checks + observability wired before cutover

## Gotchas

_Highest-signal section. Seed empty; grow it from real failures this skill
hits — `harness skills propose` suggests entries here from drift evidence._

- _none observed yet_

From ichiorca/shipsignal, Apache-2.0.

More from ichiorca/shipsignal