Atlassian Operations Terraform Provider field_mappings attribute isn't stable in integration actions

[Antoine Deschenes]

The field_mappings attribute shows drift intermittently when it contains a list of values (the responders field mapping in this example). On the terraform side, our list is always in the same order, but during state refresh, the server intermittently returns responders in a different order.

% terraform plan
atlassian-operations_api_integration.prometheus: Refreshing state... [id=...]
atlassian-operations_integration_action.create["myteam"]: Refreshing state... [id=1761859030190056731]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # atlassian-operations_integration_action.create["myaction"] will be updated in-place
  ~ resource "atlassian-operations_integration_action" "create" {
      + action_mapping           = (known after apply)
      ~ field_mappings           = jsonencode(
          ~ {
              ~ responders  = [
                  - {
                      - id   = "uuid-1"
                      - type = "team"
                    },
                    {
                        id   = "uuid-2
                        type = "team"
                    },
                  + {
                      + id   = "uuid-1"
                      + type = "team"
                    },
                ]
                # (11 unchanged attributes hidden)
            }
        )
      + group_type               = (known after apply)
        id                       = "1761859030190056731"
        name                     = "My Action"
        # (7 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

https://github.com/atlassian/terraform-provider-atlassian-operations/issues/85