Partition and VG API endpoints diverge

[Scott Hussey]

The API endpoints dealing with partitions and volume-groups both diverge when addressing collections vs single resources

Collections:
  Partitions = /api/2.0/nodes/{system_id}/blockdevices/{device_id}/partitions/
  Volume Groups = /api/2.0/nodes/{system_id}/volume-groups/

Single Resource:
  Partition = /api/2.0/nodes/{system_id}/blockdevices/{device_id}/partition/{id}
  Volume Group = /api/2.0/nodes/{system_id}/volume-group/{id}/

I would expect in a RESTful API, or even a REST-like API, that the endpoints for a collection and a resource to be identical with extra resource-id appended.

[Blake Rouse (blake-rouse)]

Are you specifically calling out the difference between?

/api/2.0/nodes/{system_id}/volume-group/{id}/

and

/api/2.0/nodes/{system_id}/volume-groups/

?

You are correct in that it should be "volume-groups". That is just a typo that was not caught in the code during implementation and code review.

[Scott Hussey (sh8121)]

Correct, just a endpoint path inconvenience. The endpoint for partition management suffers the same problem.