Ordering issue with genesyscloud_group_roles

[jmakacek]

Hello,

We have noticed some strange ordering issues with group_roles objects.

Please note:

• We made no changes to code, other than what is outlined below
• We consider this a major issue - while we could say that this would result in no changes to user experience, we cannot assume that and it is causing extra hours of development time to make sure that each change is checked/validated to make sure it won't have any impact

This example is when we attempted an upgrade from MyPureCloud client 1.23.0 to 1.25.1

Steps:

1. Ran our pipeline with 1.23.0 - resulted in "No changes. Infrastructure is up-to-date.", which is what we expected
2. Ran our pipeline with 1.25.1 - resulted in 153 objects to change

After looking into the changes it will attempt to make, it seems it is simply changing the order of the roles (please note the role_id swap), for example:

module.group_roles.genesyscloud_group_roles.xxx will be updated in-place

~ resource "genesyscloud_group_roles" "xxx" {
id = "xxx_id"
# (1 unchanged attribute hidden)

  ~ roles {
      ~ role_id      = "Role_ID_1" -> "Role_ID_2"
        # (1 unchanged attribute hidden)
    }
  ~ roles {
      ~ role_id      = "Role_ID_2" -> "Role_ID_1"
        # (1 unchanged attribute hidden)
    }
}

The example above is just a simple one, it gets much more complicated when the roles don't have the same divisions assigned, and if there are more than 2 roles.

Thank you.

[charlie.conneely]

Hello

It looks like some there were indeed some breaking changes introduced. The fix for this will be out on the next release (1.26.0) which is set for November 27th.

Thanks for reporting.

-Charlie

[jmakacek]

Thank you for your response.

I would like to add that genesyscloud_group owner_ids array does something similar (re-ordering: removing and adding the same IDs) when you change it, which sometimes results in a "tainted" object.

I was not able to reliably reproduce this, but I am sure that is is happening when you change owner_ids list, and it also happened when we were upgrading to 1.23.0.

Thank you.

[charlie.conneely]

That's strange. We'll open a ticket to take a look into that and get a fix out if we can recreate the behaviour.

Thank you

(Tracking with DEVTOOLING-248)