Inconsistency in names case sensitivity

[krismarc]

Filtering by name behaves differently. eg. apps endpoint isn't case sensitive while it matters for service instances.

cf curl "/v3/apps?space_guids=$(cf space main --guid)&names=main" | jq -c '.resources[] | [.guid, .name]'
["8675049b-7bec-4730-a97e-f4e215ae5d04","main"]
cf curl "/v3/apps?space_guids=$(cf space main --guid)&names=MAIN" | jq -c '.resources[] | [.guid, .name]'
["8675049b-7bec-4730-a97e-f4e215ae5d04","main"]

cf curl "/v3/service_instances?space_guids=$(cf space main --guid)&names=SHOVEL_MGMT" | jq -c '.resources[] | [.guid, .name]'
["e0ffd76e-0e5c-4384-bbed-63f717eb9ab5","SHOVEL_MGMT"]
cf curl "/v3/service_instances?space_guids=$(cf space main --guid)&names=shovel_mgmt" | jq -c '.pagination.total_results'
0

edit: it's not just the filter/param, case sensitivity matters for services in any aspect.

cf services | grep -i shovel
SHOVEL_MGMT rabbitmqent usage create succeeded rabbitmq-broker no
shovel_mgmt rabbitmqent usage create succeeded rabbitmq-broker no

[philippthun]

Yes, there are resources with case-insensitive names (e.g. apps) and others with case-sensitive names (e.g. service instances). This difference goes down to the database level - the name column in table apps has type citext, which is a case-insensitive string. I have no idea about the historic reasoning behind this, but I guess this is nothing that we want to change. So as long as the filter behavior is correct, I don't see anything we can do.

I've created apps and service instances and the names filter behaved correctly, i.e. case-insensitive for apps and case-sensitive for service instances.