[UX2.0] System IPv4 Device Access Policy is not behaving properly

[tzarski0]

When you configure a following resources:

resource "sdwan_policy_object_data_ipv4_prefix_list" "policy_object_data_ipv4_prefix_list" {
  entries = [
    {
      ipv4_address       = "10.123.1.1"
      ipv4_prefix_length = 32
    },
    {
      ipv4_address       = "10.123.1.2"
      ipv4_prefix_length = 32
    },
  ]
  feature_profile_id = sdwan_policy_object_feature_profile.policy_object_feature_profile.id
  name               = "jumpservers"
}

resource "sdwan_system_feature_profile" "system_feature_profile" {
  name        = "system"
  description = ""
}

resource "sdwan_system_ipv4_device_access_feature" "system_ipv4_device_access_feature" {
  default_action     = "drop"
  description        = "basic ipv4 device access policy"
  feature_profile_id = sdwan_system_feature_profile.system_feature_profile.id
  name               = "ipv4_device_access_policy"
  sequences = [
    {
      base_action                         = "accept"
      destination_ip_prefix_list_variable = "{{mgmt_loopback_ip}}"
      device_access_port                  = 22
      id                                  = 10
      name                                = "acl"
      source_data_prefix_list_id          = sdwan_policy_object_data_ipv4_prefix_list.policy_object_data_ipv4_prefix_list.id
      source_ports = [
        1000,
        2001,
      ]
    },
  ]
}

the TF apply works OK. But when you then go to UI and on device ACL hit Edit -> Save (without changing anything) then next TF apply will show a diff although it shouldn't. We should make sure the fix we develop works also for IPv6 Device Access Policy.

[seconroy]

In the UI when hitting save it changes the ID's to be sequential (1,2,3,4...) depending on the number of sequences, changing the sequence id to be 1 will fix this.