Skip to content

refactor(deployment): keep the rules that hold on any target (#2084) - #2101

Merged
braboj merged 5 commits into
mainfrom
refactor/deployment-presets
Oct 21, 2026
Merged

braboj merged 5 commits into
mainfrom
refactor/deployment-presets

Conversation

@braboj

@braboj braboj commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

infra/deployment.md keeps the deployment rules that hold on any target and drops the cloud, hybrid and offline product choices.

Section (ID kept) Before After
Targets Cloud/hybrid/offline table Declare each target in the context file; note what differs
Certificates ACM, step-ca, Vault PKI, CFSSL per target Automated renewal; expiry is an incident; roots via config management; renewal and revocation on reachable endpoints
Load balancing ALB, F5, Citrix, HAProxy, MetalLB Public ingress only via a health-checking LB or proxy; private services may resolve each other directly; prefer L7 for HTTP
DNS Route 53, BIND, Consul, etcd Resolve by name; hostnames resolve before deploy; clock sync
Registries ECR, Harbor, Athens, devpi, Verdaccio, env vars Sign and scan before production; mirror where public registries are unreachable; verify before mirroring
Secrets Cloud secret services, Vault topologies, Shamir Runtime injection; rotation; platform identity; recovery free of unreachable services; break-glass
Network Per-target assumptions Documented segments and endpoints; defined boundary crossings; firewall rules in git; hidden-call audit offline
Score Before After
deployment 95.4 99.4

Checks

  • Smoke 35/35; conformance 12 passed, 0 failed, 1 not applicable; readings read
  • Fork sync, redundancy audit, resolve, sync_docs --check, score ratchet
  • markdownlint, pre-commit hooks

Closes #2084.

🤖 Generated with Claude Code

braboj and others added 5 commits October 21, 2026 16:51
The per-target product choices leave: managed CAs, load balancer and
DNS products, registry mirrors by name, Vault topologies. Each section
keeps its ID and the target-neutral rules: automated renewal, health
checked ingress, clock sync, mirrored and verified dependencies,
runtime secrets, documented network assumptions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The rule reached private services that resolve each other directly
through service discovery, which the target-neutral rules allow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…resets

# Conflicts:
#	CHANGELOG.md
#	docs/migrating-to-v3.md
#	tests/baselines/template-quality.txt
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@braboj
braboj merged commit dbdfe7a into main Oct 21, 2026
14 checks passed
@braboj
braboj deleted the refactor/deployment-presets branch October 21, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move deployment topology presets to Imbra

1 participant