openstack
/
sahara
Code Issues Proposed changes

Unversioned endpoint recommendation 

APIv2 is reaching stability. People will want to use it. It's best,
although not actually required, if deployers put an unversioned
endpoint for Sahara in the service catalog.

Change-Id: I0256c2002c6c25969fd23cc6f6d3b11c3e577646
This commit is contained in:
Jeremy Freudberg 2018-07-12 11:42:13 -04:00
parent 9aab4b5e47
commit 8ecbeff87e
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
releasenotes/notes/sahara-endpoint-version-discovery-826e9f31093cb10f.yaml Normal file
View File

@ -0,0 +1,8 @@
---
prelude: >
- Sahara APIv2 is reaching a point of maturity. Therefore, new deployments
should include an **unversioned** endpoint in the service catalog for the
"data-processing" service, for the purposes of more intuitive version
discovery. Eventually existing deployments should switch to an unversioned
endpoint, too, but only after time is given for the use of older clients
to be less likely.