PLAT-2004: Branch-independent deployment targeting¶
Statement¶
Deployment target selection MUST come from explicit configuration or invocation, not from repository branch names.
Rationale¶
Branch-targeted deployment is confusing for OSS users and makes backend expansion harder to maintain safely.
Traceability¶
- DOCUMENTS → DOCUMENTATION
docs/architecture/root-configured-backend-bundles.md(Root-Configured Backend Bundles) - CONSTRAINS → ADR
ADR-011(OSS deployments use root-configured backend bundles) - DOCUMENTS → DOCUMENTATION
docs/architecture/branch-routing-provider-coupling-inventory.md(Branch Routing and Provider Coupling Inventory) - DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#721(Architecture: root-configured backend bundles for OSS Shifter) - DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#722(Draft requirements and ADR for root-configured backend bundles) - DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#724(Inventory branch routing and provider coupling) - DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#730(Replace branch-targeted deployment docs and CI routing) - IMPLEMENTS → CODE_FILE
.github/workflows/deploy.yml(Manual workflow_dispatch deploy with environment input (#730)) - TESTS → TEST
scripts/adr_guard/tests/test_deploy_workflow.py(TestManualDeployDispatch: push/PR never deploy; environment input selects target) - IMPLEMENTS → CODE_FILE
scripts/bootstrap/gcp_cli.py(GCP lifecycle commands select the deployment with a required --store or --inputs argument, #2571) - TESTS → TEST
scripts/bootstrap/tests/test_gcp_deploy_commands.py(The parser maps the explicit deployment source to the deploy options, #2571) - DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#2571(GitHub-less GCP deployment)