release: orchestration adopts existing infrastructure #7

Open
claude-bot wants to merge 2 commits from develop into main
Member

Release develop → main after #5: brings #6 (adopt existing infrastructure: state.keys, spec.tags, resource names, metadata.organization, pool names, extra module inputs with built-ins, plan reading existing public-ips outputs).

Validated against qtrn.io eu1-paris: plan shows 0 to add, 0 to change, 0 to destroy on both states (public-ips and cluster).

@tycho/orchestration 0.1.0 has never been published, so this release ships it as 0.1.0 with the adoption support.

🤖 Generated with Claude Code

Release develop → main after #5: brings #6 (adopt existing infrastructure: `state.keys`, `spec.tags`, resource names, `metadata.organization`, pool names, extra module inputs with built-ins, plan reading existing public-ips outputs). Validated against qtrn.io eu1-paris: `plan` shows 0 to add, 0 to change, 0 to destroy on both states (public-ips and cluster). `@tycho/orchestration` 0.1.0 has never been published, so this release ships it as 0.1.0 with the adoption support. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(orchestration): adopt existing infrastructure
All checks were successful
CI / check (push) Successful in 32s
CI / check (pull_request) Successful in 32s
b7dbfb096d
Settings to describe resources already in place, so that a target can take
over an existing installation with a plan of 0 changes:
- spec.state.keys: exact state keys (publicIps, cluster);
- spec.tags (replaces the default base tags), spec.network.ipTags,
  per-frontend tags (the module adds role and frontend itself: no more
  duplicate frontend tag);
- spec.network.vpcName, privateNetworkName, egressGatewayName;
- built-in ${VARIABLES} in the inputs of extra modules
  (e.g. ${INGRESS_<FRONTEND>_IP_ADDRESS} for a DNS module);
- SCW_PROFILE accepted for the provider, with AWS_* for the state bucket;
- plan reads the IPs of an existing public-ips state to plan the cluster.

Checked on a real platform target: both states plan with 0 changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merge pull request 'feat(orchestration): adopt existing infrastructure' (#6) from feat/orchestration-adopt into develop
All checks were successful
CI / check (push) Successful in 24s
CI / check (pull_request) Successful in 23s
2fce4e5307
Reviewed-on: #6
All checks were successful
CI / check (push) Successful in 24s
CI / check (pull_request) Successful in 23s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin develop:develop
git switch develop
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/modules!7
No description provided.