Issue with folder spelling

[muemi03]

Hi Team.
Potentially not an issue of the graphman-client, but more a graphman API issue on the gateway:
I was trying to deploy a service A in folder:
/Developers/MichaelM

The target gateway has an existing folder
/developers/michaelm

The import failed with:

{
  "data": {
    "setWebApiServices": {
      "detailedStatus": [
        {
          "action": "NEW_OR_UPDATE",
          "status": "ERROR",
          "description": "Error creating or updating SERVICE entity, Error encountered in retrieving the folder path details: (folder, name)  must be unique",
          "source": [
            {
              "name": "resolutionPath",
              "value": "/mm-ttt"
            }
          ]
        }
      ]
    }
  },
  "errors": [
    {
      "message": "Rolled back the transaction due to errors"
    }
  ]
}

It seems that the lookup of existing folders is case sensitive,
So, the import action decides to create the folder(s)
But the uniqueness constraint on folder-names is obviously case insensitive.
Hence it fails to create the new folders "Developers" and "MichaelM", because the folders "developers" and "michaelm" already exist.

Well , this explanation is just an assumption of course.

How should this issue be handled?

Thanks and kind regards
...Michael

[graju256]

@muemi03 Folder names are indeed case-sensitive. I could able to create them using policy manager and graphman.

[muemi03]

Hmm, If folder names are case sensitive, my import shouldn't fail . Right?
If a folder "developers" exist, I am not able to create a new one named "Developers" through policy manager, unless I am doing something wrong.
So, its potentially not the folder case-sensitivity, but that the uniqueness constraint seems to be case-insensitive?