azurerm_lb
- Fix adding/removing a frontend configuration forces recreation of loadbalancer issue
#19548
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.
After checking the behavior of API and Portal, in fact, it is possible to add/remove frontend configurations for existing loadbalancer, but the
zones
of existing frontend configuration could not be updated. So submitted this PR to setForceNew
to true when thezones
of the existing frontend configuration changes.Fix #19260.
Test Result:
PASS: TestAccAzureRMLoadBalancer_zonesSingle (662.43s)