release: orchestration engine, forge confirmations, CI and module publishing #5
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tycho/modules!5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Release of
developintomain. Merge with a merge commit (GitFlow), not squash.Content
orchestration: targets fromtarget.yaml, guided run (durable IPs → DNS stop → reverse DNS → cluster → kubeconfig and marker → stacks), Terraform roots from the catalogue modules, guards (saved plans, no destroy).orchestration: exact pool names, Scaleway key/project check, organisation-aware targets (org/name), pools start at their minimum, confirmations through the core (no--yes).forge: confirmation of every destructive command (pr merge, mirror sync, git force/delete/reset --hard…, gh/tea/glab delete/close…).@tycho/<module>@X.Y.Ztags.After the merge
PACKAGES_TOKEN(write:package) must exist for the release workflow.@tycho/forgeis 1.0.0;@tycho/orchestrationis still 0.1.0 in itspackage.json: bump it in a PR ondevelopbefore tagging it (it requires core^1.0.0, the core withctx.targetandctx.confirm).main:@tycho/forge@1.0.0, then@tycho/orchestration@<version>.🤖 Generated with Claude Code
Replaces the shell placeholder with the engine of RFC-001 §3: - target.yaml: types and fail-fast validation (every problem listed, no default for instance values, placeholders and branch refs refused); - contexts: one tycho manages several targets (context add/use/list, --target, TYCHO_TARGET); one kubeconfig per target, 0600, outside the repo; - catalogues fetched at a pinned ref; Terraform roots generated from the catalogue modules: durable public IPs and cluster, each in its own state; - guided run: public IPs, stop until DNS records exist, reverse DNS, cluster, kubeconfig and ownership marker, stacks in requires order; - guards: saved plans only, any destroy or replace refused, confirmation before each apply, cluster ownership checked before every kubectl change; - stacks: ${VARIABLE} substitution limited to declared and built-in names, secrets only from SOPS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>