r/aws_vpc: Add wait_for_ipam_deallocation parameter #34628
+14
−1
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.
Description
The wait for IPAM pool deallocation was introduced in #30795.
This allows force-recreation of VPC whose CIDR is IPAM-managed to succeed by waiting for IPAM to reach eventual consistency.
Better explanation of the reasoning behind this change can be found here: #31211 (comment)
The problem is that IPAM deallocation takes significant amount of time. For certain use-cases waiting for IPAM can be skipped, like final destroy of the VPC.
This PR introduces a parameter
wait_for_ipam_deallocation
which defaults totrue
(current behavior). Thus, if user thinks the wait just adds up execution time unreasonably,wait_for_ipam_deallocation = false
could be passed to vpc resource.Relations
Closes #31211
Relates #27571
References
#30795
Output from Acceptance Testing