fix(azure/postgresql): allow deploy role to register resource providers#221
fix(azure/postgresql): allow deploy role to register resource providers#221tfelix wants to merge 1 commit into
Conversation
The PostgreSQL building block deploy role only granted Microsoft.DBforPostgreSQL/* actions. On a freshly created subscription the DBforPostgreSQL resource provider is not yet registered, and the first deployment fails because the deploy role cannot register it. Add "*/register/action" so the deploy role can register the required resource providers, matching the pattern already used by the other Azure backplane modules (e.g. storage-account, key-vault). Co-Authored-By: Claude Opus 4.8 (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). |
The PostgreSQL building block deploy role only granted Microsoft.DBforPostgreSQL/* actions. On a freshly created subscription the DBforPostgreSQL resource provider is not yet registered, and the first deployment fails because the deploy role cannot register it.
Add "*/register/action" so the deploy role can register the required resource providers, matching the pattern already used by the other Azure backplane modules (e.g. storage-account, key-vault).