azurerm_public_ip_prefix
: Update prefix_length
validation to accept all valid IPv4 address ranges
#6589
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.
Feb 11, 2020 there was a change to the resource to restrict the range to be between 28 and 31 due to the product documentation which states that by default /28 is the maximum limit, however also in the documentation it states that you should contact customer support to change the default limit of /28.
Since there is no way for terraform to know the approved range for a given subscription I have opened up the validation to check that the passed value is between
0
and31
, which should cover all possible IPv4 scenarios.