azurerm_virtual_network_gateway_connection
- set ingress_nat_rule_ids
in the update operation
#27022
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.
Community Note
Description
TF should set the ingressNatRules property in the request payload for
ingress_nat_rule_ids
but actually TF would set the egressNatRules property wheningress_nat_rule_ids
is changed. This bug is introduced by PR. So I submitted this PR to fix it.PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_virtual_network_gateway_connection
- setingress_nat_rule_ids
in the update operationThis is a (please select all that apply):
Related Issue(s)
Fixes #27009
Note
If this PR changes meaningfully during the course of review please update the title and description as required.