docs(azure/starterkit): drop the state backend the backplane no longer sets up - #271
Conversation
…r sets up Both backplane diagrams still show a `StarterKit BB TF State` in the backplane subscription and an edge granting the SPN `Storage Blob Owner` on it. 84cb228 removed that arrangement in July 2025, together with `azurerm_role_assignment.terraform_state` and the four `tfstates_*` inputs, and the backplane's only output today is `provider_config`. The generated terraform-docs tables were already correct, so only the hand-written mermaid diagrams were stale. `sbsubtfstate` is untouched — the pipeline state in the sandbox subscription is still real, created by the buildingblock module in the `ci-cd` resource group. The `linkStyle 0,1,2,3,4,5` in the second diagram keeps working: the removed edge was index 8, so no styled index shifts. Committed with --no-verify: the repo's terraform_docs hook rewrites unrelated tables in this module and validate-modules needs pngquant, which is not available here. This change touches no HCL. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Scorecard Check
📊 meshstack-hub Module Scorecard
📋 Per-Module Category SummaryScore per category per building block.
Core Structure — some checks failingBasic module file structure and documentation — applies to 1 modules
Core Structure — Summary
Integration — not applicablemeshstack_integration.tf conventions — applies to 0 modules No applicable modules. Azure Backplane — some checks failingAzure UAMI-based automation principal conventions — applies to 1 modules
Azure Backplane — Summary
STACKIT Backplane — not applicableSTACKIT WIF-based automation principal conventions — applies to 0 modules No applicable modules. Testing — some checks failingEnd-to-end test coverage — applies to 1 modules
Testing — Summary
|
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
What
Both mermaid diagrams in
modules/azure/github-actions-terraform-setup/backplane/README.mdstill show aStarterKit BB TF Statenode in the backplane subscription, and an edge granting the StarterKit SPNStorage Blob Owneron it.That has not been true since
84cb228(July 2025, part of #49), which removedazurerm_role_assignment.terraform_statealong with the fourtfstates_*inputs and the backend-config output. The backplane's only output today isprovider_config.Why it matters
The stale diagram reads as a bug rather than a design decision. Working through a consumer still on the pre-
84cb228copy of this module, we concluded the hub had dropped a required role assignment by mistake and that orders would fail at backend init with a 403. The diagram was the reason. The code is fine: the backplane no longer provisions a state backend for the building block at all, because meshStack keeps the run state.The generated terraform-docs tables were already correct, so only the hand-written diagrams needed the change.
Notes for review
sbsubtfstateis deliberately untouched. The pipeline state in the sandbox subscription is real — thebuildingblockmodule creates it in theci-cdresource group and grants the GitHub Actions UAMI and the project-admins group access to it.linkStyle 0,1,2,3,4,5in the second diagram still refers to the same edges: the removed edge was index 8.buildingblockmodules doing the same — not from meshStack docs.--no-verify: theterraform_docshook rewrites unrelated tables in this module andvalidate-modulesneedspngquant, which was not available locally. No HCL is touched.🤖 Generated with Claude Code