meraki_networks_appliance_vlans somehow trigger to be updated after adding manually appliance warm spare on meraki dashboard

[efernando87]

Prerequisites

• [V] Have you tested the operation in the API directly?
• [V] Do you have the latest Terraform provider version?
• [V] Review the compatibility matrix before opening an issue.

Describe the bug after adding the warm spare on meraki dashboard, the terraform plan/apply showing config changes on the meraki_networks_appliance_vlans plugin part interface id (example below)

 # module.network.meraki_networks_appliance_vlans.example_vlan[0] will be updated in-place
  ~ resource "meraki_networks_appliance_vlans" "example_vlan" {
      + dhcp_relay_server_ips     = (known after apply)
        id                        = "224"
      ~ interface_id              = "3686196295003347754" -> (known after apply)
      + ipv6                      = {
          + enabled            = false
          + prefix_assignments = (known after apply)
        }
        name                      = "EXAMPLE-VLAN"
        # (17 unchanged attributes hidden)
    }

this config change also triggered to other vlans configured previously. and if we apply the config change, it will throw plugin error as attached file error message meraki_networks_appliance_vlans.pdf

if we remove the warm spare device from the meraki dashboard site, it will remove config changes on the terraform plan/apply

Expected behavior terraform plan not showing any changes or the terraform apply works

Screenshots please find the attached .pdf file for the error messages

Environment (please complete the following information):

• Meraki Dashboard version:
• Terraform version: v1.8.3
• Meraki provider version: 0.2.5-alpha
• OS Version:

Additional context Add any other context about the problem here.

[fmunozmiranda]

@efernando87 please try it again with new version and update us.

[fmunozmiranda]

If we do not receive a response it will be closed in the next 24 hours.