Ensure enable_http2 works when targeting existing Application Gateways #1439
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
Fred-sun
added
ready_for_review
xuzhang3
approved these changes
Mar 22, 2024
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.
SUMMARY
We've found that, when deploying an application gateway using bicep templates, if the enable_http2 parameter is not specified it will make any kind of request to retrieve the status of that particular AppGW to not return the enable_http2 parameter status. We've verified that using the azcli and the API directly.
This makes any attempt to manage an existing AppGW deployed through the aforementioned means to fail since the
old_responsedoesn't have theenable_http2key.ISSUE TYPE
COMPONENT NAME
azure_rm_appgateway