Templates Constantly Locked

[HSPm]

Heyo 👋

I'm editing a couple of feature templates, and these feature templates are used in 2 device templates, and each of those device templates are attached to 2 devices (So 1 device template each).

From the provider doco

This provider supports updates to a single feature template, device template and policy per device within a single terraform apply operation

How does this work with multiple devices? Is it just not compatible ? I've done A LOT of applies to no avail.

I'm updating a couple of sdwan_cisco_vpn_interface_feature_template address_variable names and making the similar change to my sdwan_attach_feature_device_template variables

eg.
Multiple feature template changes as such 👇

   # module.feature_templates.sdwan_cisco_vpn_interface_feature_template.... will be updated in-place
  ~ resource "sdwan_cisco_vpn_interface_feature_template" "..." {
      ~ address_variable                      = "vpn_if_ipv4_address" -> "vpn0_loopback_ipv4_address"
        id                                    = ""
        name                                  = ""
      ~ version                               = 0 -> (known after apply)
        # (10 unchanged attributes hidden)
    }

And a couple of device template attachment changes as such 👇

   # module.device_templates.sdwan_attach_feature_device_template.... will be updated in-place
  ~ resource "sdwan_attach_feature_device_template" "..." {
      ~ devices = [
          ~ {
                id        = ""
              ~ variables = {
                  + "vpn0_loopback_ipv4_address" = "<ip cidr>"
                  - "vpn_if_ipv4_address"          = "<ip cidr>" -> null
                    # (3 unchanged elements hidden)
                }
            },
        ]
        id      = ""
      ~ version = 6 -> (known after apply)
    }

And the error I'm constantly getting is 👇

 Warning: Client Warning

  with module.feature_templates.sdwan_cisco_vpn_interface_feature_template....,
  on modules/feature-templates/vpn-interface.tf line 41, in resource "sdwan_cisco_vpn_interface_feature_template" "...":
  41: resource "sdwan_cisco_vpn_interface_feature_template" "..." {

Failed to modify template due to template being locked by another change.
Template changes will not be applied. Re-run 'terraform apply' to try again.

Is there something I'm missing here 😅

[tzarski0]

Hi @HSPm, thanks for submitting the issue. Let's focus on a single device template to make it easier. For a single device template, how many interface templates are you modifying? The UX 1.0 API requires sequential updates. If you modify multiple feature templates:

1. The first terraform apply will modify one of them and should trigger a template attachment while other changes will end up with "Client Warning ...template being locked by another change".
2. The next time you run an apply you should no longer see any diff for the first feature template that you applied, but other diff should still be visible.
3. Each run you run an apply, one feature template would be modified and pushed, so you should see less and less changes with each apply.

It should work in similar way when you modify a single feature template attached to multiple device templates.

[HSPm]

Hi @tzarski0,
I'm updating the variable name of ~8 feature templates which are used by both device templates.

If I focus on 1 device template (remove 1 device template and its accompanying device attachment from tf state), won't that cause issues with the 2nd device template variables ?

At the moment all of the feature templates use the same vpn_if_ipv4_address variable, I'm updating each of these to be more unique, hence why I'm updating both feature templates & device attachments.

From a networking as code aspect, what should be the right course of action here since this is a limitation from the underlying UX 1.0 API?

[tzarski0]

If you modify just one feature template that is assigned to multiple device templates and update variables for multiple devices, this should work without any issues. The lock situation might happen only if you change multiple feature templates that are part of the same device template.