When changing unique_name of a twilio_verify_services_rate_limits_v2 resource, in-place update is planned. Such plan applies successfully, however unique_name does not get updated. Looking at the Update a Rate Limit API documentation, it does not seem to be supported.
4. Perform GET request to `https://verify.twilio.com/v2/Services/VAXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/RateLimits/` and notice how `description` is updated, but `unique_name` is not.
### Expected Behaviour
Expected behaviour would be to fail with an error (at least at Apply Time) rather than return success despite silently failing. We would also expect the provider to be smart enough to handle converting the plan to a destroy/recreate operation if it can't update the attribute in place.
### Technical details:
* terraform-provider-twilio version: 0.18
* terraform version: 1.2.0
Issue Summary
When changing
unique_name
of atwilio_verify_services_rate_limits_v2
resource, in-place update is planned. Such plan applies successfully, howeverunique_name
does not get updated. Looking at the Update a Rate Limit API documentation, it does not seem to be supported.Steps to Reproduce
Create a rate limit
Update
unique_name
Notice how this is planned as update in-place....
..... and successfully applied:
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.