Fix Azure deploy Terraform state authorization permanently#55
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this fixes\n- hardens Terraform state storage reachability for GitHub runners\n- resolves OIDC principal deterministically from AZURE_CLIENT_ID\n- ensures Blob Data Contributor on storage account and container scopes\n- adds state data-plane preflight before each provision attempt\n- treats backend AuthorizationFailure/listing-blobs init errors as retryable\n\n## Why this is permanent\n- removes dependency on fragile one-time RBAC timing\n- auto-remediates network default-action deny for the state account in CI\n- validates data-plane readiness before invoking azd provision\n\n## Expected outcome\n- Azure Deploy (azd) no longer fails at Terraform backend init with 403 AuthorizationFailure in normal OIDC propagation scenarios