You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be more of an issue with the Twilio API than the Terraform provider directly, but if so, the provider does not correctly handle cidr_prefix_length = 0 during plans. The API appears to overwrite this with a /32, which then leads to drift on every run.
Steps to Reproduce
Use the below code snippet to create a couple of resources in the Twilio console.
The apply will run successfully, but the Twilio console will show that the below access control list was created as 0.0.0.0/32; not the expected 0.0.0.0/0.
Subsequent plans now show that cidr_prefix_length drifts, and Terraform is never able to correct this.
As a workaround, creating two access control lists with prefixes of 0.0.0.0/1 and 128.0.0.0/1 respectively works, however this is confusing.
Expected Behavior
Either:
A. The API should support wildcards (0.0.0.0/0) and thus the above code works as expected (preferred)
B. The Terraform provider should fail validation on the above code because the API does not support /0s and the API should return a 4XX to indicate that it isn't supported.
The text was updated successfully, but these errors were encountered:
Issue Summary
This may be more of an issue with the Twilio API than the Terraform provider directly, but if so, the provider does not correctly handle
cidr_prefix_length = 0
during plans. The API appears to overwrite this with a /32, which then leads to drift on every run.Steps to Reproduce
0.0.0.0/32
; not the expected0.0.0.0/0
.cidr_prefix_length
drifts, and Terraform is never able to correct this.Code Snippet
Technical details:
Workaround
As a workaround, creating two access control lists with prefixes of
0.0.0.0/1
and128.0.0.0/1
respectively works, however this is confusing.Expected Behavior
Either:
A. The API should support wildcards (0.0.0.0/0) and thus the above code works as expected (preferred)
B. The Terraform provider should fail validation on the above code because the API does not support /0s and the API should return a 4XX to indicate that it isn't supported.
The text was updated successfully, but these errors were encountered: