Updating an oci_os_management_hub_managed_instance_group resource should not trigger change if the only variation from the previous resource is order of the software_source_ids. The order is not relevant to how the group operates and therefore can/should be allowed change without impact.
Actual Behavior
If an oci_os_management_hub_managed_instance_groupresource is updated it will always trigger a change based on the order ofsoftware_source_ids`. Notably, the order of the IDs for the resource initially created does not align to the order of the input values (via list(string)) so, as is, the order is unpredictable even if one wanted to manually re-order to avoid the issue
Steps to Reproduce
terraform apply
terraform apply again and note trigger to change even though nothing has changed. Is triggered only because the order of software_source_ids in the created resource now does not match what was provided on input to create the resource
Manually re-order the software_source_ids input then terraform apply and note again will be prompted to accept a change (though no functional change has occurred).
Community Note
Terraform Version and Provider Version
Affected Resource(s)
affected_resources = oci_os_management_hub_managed_instance_group
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Updating an
oci_os_management_hub_managed_instance_group
resource should not trigger change if the only variation from the previous resource is order of thesoftware_source_ids
. The order is not relevant to how the group operates and therefore can/should be allowed change without impact.Actual Behavior
If an oci_os_management_hub_managed_instance_group
resource is updated it will always trigger a change based on the order of
software_source_ids`. Notably, the order of the IDs for the resource initially created does not align to the order of the input values (via list(string)) so, as is, the order is unpredictable even if one wanted to manually re-order to avoid the issueSteps to Reproduce
terraform apply
terraform apply
again and note trigger to change even though nothing has changed. Is triggered only because the order ofsoftware_source_ids
in the created resource now does not match what was provided on input to create the resourcesoftware_source_ids
input thenterraform apply
and note again will be prompted to accept a change (though no functional change has occurred).Important Factoids