Draft
Conversation
RMcVelia
force-pushed
the
main-azurerm-v4
branch
3 times, most recently
from
123017a to
0f172c3
Compare
RMcVelia
force-pushed
the
main-azurerm-v4
branch
from
0f172c3 to
470669f
Compare
4 tasks
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
1 participant
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.
Context
Updating the azurerm provider from version 3 to version 4
Changes proposed in this pull request
We can't support both versions from the same modules, so while we upgrade services we will have the following 3 branches
As we update each service, we will point to the branches above.
Any additions should be applied in separate commits.
terraform module changes that are applied to the v3 main, testing and stable should be applied to the v4 branches in the same order (rebase from the v3 branch).
Once all services are updated, the v4 specific commits will be applied to main, testing and stable, and then the v4 branches can be removed.
This PR is not to be merged.
Checklist
Devopslabel