yahoo-eng-team team mailing list archive

[Boden R <bodenvmw@xxxxxxxxx>]

Public bug reported:

This is a feature request for API extensions.

Based on the discussion in [1], it seems there maybe some use in
introducing a 'api_status' attribute on all API extensions. This
attribute would be defined in the API's definition
(neutron_lib.api.defintions.<ext>) and would be returned in the
extension body(s) for GETs (/v2.0/extensions, /v2.0/extensions/{alias}).

The api_status should be a static set of values. For example:
- EXPERIMENTAL --> The API is in "beta mode" and not fully hardened.
- SUPPORTED --> Current supported API.
- DEPRECATED --> The API is not actively supported any maybe removed in a future release.


[1] https://review.openstack.org/#/c/415817/

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1698907

Title:
  [RFE] Add 'api_status' attribute to API extensions

Status in neutron:
  New

Bug description:
  This is a feature request for API extensions.

  Based on the discussion in [1], it seems there maybe some use in
  introducing a 'api_status' attribute on all API extensions. This
  attribute would be defined in the API's definition
  (neutron_lib.api.defintions.<ext>) and would be returned in the
  extension body(s) for GETs (/v2.0/extensions,
  /v2.0/extensions/{alias}).

  The api_status should be a static set of values. For example:
  - EXPERIMENTAL --> The API is in "beta mode" and not fully hardened.
  - SUPPORTED --> Current supported API.
  - DEPRECATED --> The API is not actively supported any maybe removed in a future release.

  
  [1] https://review.openstack.org/#/c/415817/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1698907/+subscriptions