feat: ./azurerm/coverage/tf.json update process#164
Merged
Conversation
…form-reports commit 26ffa71521c4bdf852b1cc5b0c6ee045fa036bba
…v0.3.1-0.20260715003534-2c6101a24b3e
hqhqhqhqhqhqhqhqhqhqhq
approved these changes
Jul 17, 2026
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
2 participants
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.
Migrated ./azurerm/coverage/tf.json update process from the release pipeline into a manual step in this repo due to reliance on insecure PAT.
Also updated the tf.json, supported azurerm provider version and aztft dependency.
I will raise a follow PR to our internal doc for the release process.
Testing
Ran
make testto ensure functionality works ✅