TO API: Message returned from API in Server server capabilities should be corrected

[lbathina]

I'm submitting a ...

• [ ] bug report
• [ ] new feature / enhancement request
• [X] improvement request (usability, performance, tech debt, etc.)
• [ ] other

Traffic Control components affected ...

• [ ] CDN in a Box
• [ ] Documentation
• [ ] Grove
• [ ] Traffic Control Client
• [ ] Traffic Monitor
• [x] Traffic Ops
• [ ] Traffic Ops ORT
• [ ] Traffic Portal
• [ ] Traffic Router
• [ ] Traffic Stats
• [ ] Traffic Vault
• [ ] unknown

Current behavior:

When a server is associated with capability that is already associated , we get server_server_capability server, server_capability '151, TEST_DISK2' already exists.

this exposes the database tables and fields and is not user friendly.

Expected / new behavior:

The message could be Server Capability <capability name> is already associated with server <Servername>.

Minimal reproduction of the problem with instructions:

create server capability associate server capability to server try associate the same server capability to server

Anything else:

[mitchell852]

This is really something that has to be changed in the TO API and not TP. TP only displays the message it gets from the TO API.

[ocket8888]

I believe that's a limitation of the "CRUDer", and probably manifests in many endpoints.