release: orchestration adopts existing infrastructure #7
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!7
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 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:
planshows 0 to add, 0 to change, 0 to destroy on both states (public-ips and cluster).@tycho/orchestration0.1.0 has never been published, so this release ships it as 0.1.0 with the adoption support.🤖 Generated with Claude Code
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>View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.