volterra_public_ip usage unclear

[michaelbuemi]

This can't be used to create a public IP address which makes sense. However, its existence implies that I should be able to safely use it to update a public IP's virtual_site. Since virtual_sites can't be edited, one has to create new ones and then swap the virtual_site on a public IP.

It would be a reasonable workflow to import the public_ip to state after manual creation. as you could then modify its properties.

However, as this resource doesn't support import, we can't do that.

terraform import -ignore-remote-version volterra_public_ip.ip_192_0_2_1 ip-192-0-2-1
╷
│ Error: resource volterra_public_ip doesn't support import
│
│
╵

Even more confusingly, the provider lets you modify a public_ip if you try to just add the config sans import but throws an error:

volterra_public_ip.192_0_2_1: Creating...
2024-11-05T21:55:46.804Z [ERROR] vertex "volterra_public_ip.ip_192_0_2_1" error: Provider produced inconsistent result after apply
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to volterra_public_ip.ip_192_0_2_1, provider
│ "provider[\"registry.terraform.io/volterraedge/volterra\"]" produced an
│ unexpected new value: Root object was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵
Operation failed: failed running terraform apply (exit 1)

This resulted in the correct modification of the public_ip to use the new virtual_site I created.