Bug 1041876 - [RFE][keystone]: Deprecate support for Identity API v2.0
Summary: [RFE][keystone]: Deprecate support for Identity API v2.0
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M1
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Udi Kalifon
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_icehouse-1 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:50 UTC by RHOS Integration
Modified: 2016-04-26 17:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-05 13:31:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 19:50:22 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/deprecate-v2-api.

Description:

Given Identity API v3's feature parity with v2.0 and several of it's extensions (specifically OS-KSCRUD, OS-KSADM), it's time to deprecate support for the controllers supporting these features. Legacy controller methods should log a deprecation warning about their continued use while we work to upgrade clients.

Specification URL (additional information):

None
Comment 2 Stephen Gordon 2014-01-23 20:47:51 UTC 
Moving to POST based on upstream status (Implemented).
Comment 3 Udi Kalifon 2014-03-31 06:21:14 UTC 
The deprecation message should not appear any more starting from Icehouse rc-1. Support for V2.0 API will be extended until K.
Comment 4 Udi Kalifon 2014-04-27 12:23:15 UTC 
Verfied that the deprecation messages are indeed no longer showing: openstack-keystone-2014.1-2.el7.noarch
Comment 5 Udi Kalifon 2014-05-04 07:06:13 UTC 
No need for doc text, as the deprecation of the API v2.0 has been postponed and Icehouse will continue to support v2.0 as always.
Comment 6 Adam Young 2014-05-05 13:31:27 UTC 
As Udi said, this is not happening.  We will open a new bug when deprecation actually is on the schedule.
Note You need to log in before you can comment on or make changes to this bug.