Mark domain-config API as experimental in Identity spec

Bug #1429557 reported by Henry Nash
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Henry Nash

Bug Description

Since the domain-config API is very recent, it makes sense to mark it as experimental. Further, our goal of migrating away from the concept of extension includes the support of marking individual APIs as experimental, deprecated etc. - however, we do not describe how a user of the API can discover this.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to keystone-specs (master)

Fix proposed to branch: master

Changed in keystone:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to keystone-specs (master)

Submitter: Jenkins
Branch: master

commit c30458fba68d86e91d269dcfde1fd004d07a7776
Author: Henry Nash <email address hidden>
Date: Sun Mar 8 17:51:05 2015 +0000

    Mark the domain-config API as experimental

    We should consider the domain-config resouces and APIs as
    experimental, so as well as indicating this is the spec, we should
    describe how a caller can determine this via the API.

    Change-Id: I112aff129aceef506aead28379e81034fd41d4c6
    Closes-bug: 1429557

Changed in keystone:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in keystone:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in keystone:
milestone: kilo-3 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.