Fix updating vcd_external_network_v2 with edge gateway having dedicate_external_network=true
#1301
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.
Closes #1183
About the problem
There is a bug in runtime validation that is triggered when all of the following conditions are met:
dedicate_external_network = true
static_ip_pool
) [this is when the bug described in Error: could not get network data: 'dedicated_org_id' modifying "vcd_external_network_v2" resource #1183 is hit]Fix
The fix is to ignore validation
!usingIpSpace && d.Get("dedicated_org_id").(string) != ""
during update becaused.Get("dedicated_org_id")
might return the value of computed field which automatically gets populated when edge gateway consumes this network (hasdedicate_external_network = true
).Sample hcl
Replicating
commit da78097 has a test that hits the issue