When issuing the "pcs constraints" command and you have one or multiple resource sets configured, the resources in the resource set are ordered alphabetically if the default "text" output format is used.
They are supposed to match the order in the CIB, as the cluster takes actions based on the order in which resources are in the CIB, the other output formats do respect the order of the resources in the CIB.
This creates confusion.

For example:
$ sudo pcs constraint --full
Colocation Set Constraints:
  Set Constraint: colocation_set-nfs_server
    score=INFINITY
    Resource Set: colocation_set-nfs_server_set
      Resources: 'nfs_data_drbd-clone'
      role=Promoted
    Resource Set: colocation_set-nfs_server_set-1
      Resources: 'nfs_data_animaletti', 'nfs_data_infodir', 'nfs_data_multimedia', 'nfs_data_software', 'nfs_export_animaletti', 'nfs_export_multimedia', 'nfs_export_root', 'nfs_export_software',
          'nfs_ipv4', 'nfs_ipv6', 'nfs_server'
Order Set Constraints:
  Set Constraint: order_set-nfs_server
    Resource Set: order_set-nfs_server_set
      Resources: 'nfs_data_drbd-clone'
      action=promote
    Resource Set: order_set-nfs_server_set-1
      Resources: 'nfs_data_animaletti', 'nfs_data_infodir', 'nfs_data_multimedia', 'nfs_data_software', 'nfs_export_animaletti', 'nfs_export_multimedia', 'nfs_export_root', 'nfs_export_software',
          'nfs_ipv4', 'nfs_ipv6', 'nfs_server'
      action=start

$ sudo pcs constraint --output-format=json
{
  "location": [],
  "location_set": [],
  "colocation": [],
  "colocation_set": [
    {
      "resource_sets": [
        {
          "set_id": "colocation_set-nfs_server_set",
          "sequential": null,
          "require_all": null,
          "ordering": null,
          "action": null,
          "role": "Promoted",
          "score": null,
          "kind": null,
          "resources_ids": [
            "nfs_data_drbd-clone"
          ]
        },
        {
          "set_id": "colocation_set-nfs_server_set-1",
          "sequential": null,
          "require_all": null,
          "ordering": null,
          "action": null,
          "role": null,
          "score": null,
          "kind": null,
          "resources_ids": [
            "nfs_data_infodir",
            "nfs_data_software",
            "nfs_data_animaletti",
            "nfs_data_multimedia",
            "nfs_ipv4",
            "nfs_ipv6",
            "nfs_server",
            "nfs_export_root",
            "nfs_export_software",
            "nfs_export_multimedia",
            "nfs_export_animaletti"
          ]
        }
      ],
      "attributes": {
        "constraint_id": "colocation_set-nfs_server",
        "score": "INFINITY",
        "influence": null,
        "lifetime": []
      }
    }
  ],


Reproducible: Always

Steps to Reproduce:
1. Create a Pacemaker cluster
2. Create some resources and resource constraints sets for ordering or colocation
3. issue pcs constraint
Actual Results:
resources are ordered alphabetically instead of the order in the CIB

Expected Results:
resources are ordered literally as in the CIB