manila/releasenotes/notes/api-versions-mark-v1-deprecated-3540d39279fbd60e.yaml
Goutham Pacha Ravi 6ba74918d5 Mark 'v1' API deprecated in the versions response
We announced the deprecation of the v1 API on
the mailing list during the mitaka release. While we
continue to support it in code and run CI tests on it,
we should allow the consumers of the versions API to
acknowledge this change.

This patch does not remove the API. It only marks the
version as "DEPRECATED".

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-June/096517.html

Change-Id: If80bddb68a5b92b604ef582fe07eef72c47d6f2f
2017-01-27 14:12:39 +00:00

12 lines
732 B
YAML

---
deprecations:
- Deprecation of the manila v1 API was announced in the mitaka release.
The versions response from the API has been fixed to state that this
version has been deprecated. If you are using v1 API, consider switching
to the v2 API to take advantage of newer features. v2 API has support for
'microversions'. Any endpoint on the v2 API can be requested with the HTTP header
'X-OpenStack-Manila-API-Version' and providing a value '2.x', where '2' is the
major version and 'x' is the minor (or 'micro') version. To continue exploiting
feature functionality that was part of the v1 API, you may use the v2 API with
the microverison '2.0', which is behaviourally identical to the v1 API.