Pass through gateway preservation settings - #125
Merged
Conversation
lyudmililchev92
approved these changes
Jun 25, 2026
martinvladimirov220116
force-pushed
the
release/v1.4.2
branch
from
June 25, 2026 12:32
d8af8a8 to
0bef626
Compare
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.
Summary
Preserves existing Azure Application Gateway global buffering settings and VPN connection custom BGP addresses by passing those tfvars settings through to the underlying AzureRM resources.
Changes
globalonazurerm_application_gateway.request_buffering_enabledandresponse_buffering_enabled.custom_bgp_addressesonazurerm_virtual_network_gateway_connection.primaryandsecondarycustom BGP addresses.