Manila API does not accepts "latest" as api version

[Sebastien Derrey]

Hello!

Description
===========
Compared to other Openstack modules like Nova, Manila does not accept "latest" keyword for the version. It would be very useful for us to not have to hardcode a version number in our codebase using the Manila API.
Is there a reason why it has not been implemented?

Step to reproduce
===========

for any call to manila, set version value to "latest" in the dedicated header: X-Openstack-Manila-Api-Version: latest

Expected result
===========

If latest is specified, would take the latest version automatically, eg: 2.78

Actual result
===========

The request send back the error: {"badRequest": {"code": 400, "message": "API Version String latest is of invalid format. Must be of format MajorNum.MinorNum."}}

Environment
===========

The code in question looking for MajorNum.MinorNum version formatting in Manila:
https://github.com/openstack/manila/blob/0c8cc2333b881af3cb3206d2a45f52aab5e77ff5/manila/api/openstack/wsgi.py#L240

Example of implementation of latest in Nova:
https://github.com/openstack/nova/blob/master/nova/api/openstack/wsgi.py#L162

Thank you very much!

[Carlos Eduardo (silvacarlose)]

We will discuss this at the Dalmatian PTG. This request has been denied in the past but we can re-evaluate.

[Vida Haririan (vhariria)]

See additional triage information at https://meetings.opendev.org/meetings/manila/2024/manila.2024-03-28-15.00.log.html