Set RawConfig on the diff state #319
Merged
Conversation
This file contains 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
Signed-off-by: Alper Rifat Ulucinar <[email protected]>
sergenyalcin
approved these changes
Dec 27, 2023
There was a problem hiding this comment.
Thanks @ulucinar LGTM. I validated this change by testing the network.WebApplicationFirewallPolicy resource.
1 task
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.
Description of your changes
This PR proposes a change where we start setting the
RawConfig(in addition to theRawPlanwe already set) on the diff state we use while computing theterraform.InstanceDiffs. @sergenyalcin has observed the need to do so while validating theazurerm_web_application_firewall_policyresource with the new upjet runtime architecture.I have:
make reviewableto ensure this PR is ready for review.backport release-x.ylabels to auto-backport this PR if necessary.How has this code been tested
Tested manually against the
azurerm_web_application_firewall_policyresource inupbound/provider-azure.