volterra_securemesh_site_v2 node_list issues

[s-archer]

There are a few issues with the volterra_securemesh_site_v2, two of which relate to the node_list.

The first issue occurs when updating the resource configuration (performing an apply operation on an existing resource after changing the resource configuration). The issue arises because of a conflict (two sources-of-truth) between Terraform and the F5 XC Platform.

The Terraform volterra_securemesh_site_v2 resource does not allow the inclusion of a node_list, so it is effectively equal to null. The node_list is actually populated by XC when the nodes register themselves with the platform, but Terraform is unaware of this. If Terraform is applied a second time, it overwrites the XC populated node_list with its own null version.

The net result is that you cannot modify an SMSv2 site with Terraform, becasue it removes node_list config and breaks the site.

The second issue is a similar problem with labels. After site deployment, F5 XC adds labels that Terraform is unaware of. This causes Terraform to detect a change, and on next apply, will try and update the volterra_securemesh_site_v2resource. It is currently necessary to use a lifecycle block to ignore label changes.

The third issue is that the Terraform volterra_securemesh_site_v2 resource does not allow the inclusion of a node_list, you cannot configure SMSv2 nodes with Terraform at all, which prevents use of segments.