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
{{ message }}
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.
Apply the above config, change the name to test-updated and then re-apply
Expected Behavior
Updating the resource name should force creation of a new resource. The original opc_compute_ip_reservation should be destroyed and a new resource created with the new name.
Actual Behavior
Terraform tries to update the name, but the apply fails
Terraform will perform the following actions:
~ opc_compute_ip_reservation.test
name: "test" => "test-updated"
Plan: 0 to add, 1 to change, 0 to destroy.
opc_compute_ip_reservation.test: Modifying... (ID: test)
name: "test" => "test-updated"
Error: Error applying plan:
1 error(s) occurred:
* opc_compute_ip_reservation.test: 1 error(s) occurred:
* opc_compute_ip_reservation.test: doesn't support update
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Change name from test to test-updated
terraform apply
The text was updated successfully, but these errors were encountered:
Affected Resource(s)
Terraform Configuration Files
Apply the above config, change the name to
test-updated
and then re-applyExpected Behavior
Updating the resource name should force creation of a new resource. The original
opc_compute_ip_reservation
should be destroyed and a new resource created with the new name.Actual Behavior
Terraform tries to update the name, but the apply fails
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
name
fromtest
totest-updated
terraform apply
The text was updated successfully, but these errors were encountered: