Give a prospective removal date for all v2 APIs
All the v2 APIs are marked as deprecated, but the v2_auth and v2_ec2 did not have proposed removal dates. In keeping with the general standards, the earliest we can do this is Pike + 4, although we specify this as Mitaka + 7 so as not to change the actual release version we first marked these as deprecated. Change-Id: I1d8c5e43ff7c8e4256639324db47a64635e217df Implements: bp removed-as-of-pike
This commit is contained in:
parent
1d4c72cd6f
commit
b87cdc28df
@ -54,7 +54,7 @@ def v2_ec2_deprecated(f):
|
||||
what=f.__name__ + ' of the v2 EC2 APIs',
|
||||
as_of=versionutils.deprecated.MITAKA,
|
||||
in_favor_of=('a similar function in the v3 Credential APIs'),
|
||||
remove_in=0)
|
||||
remove_in=+7)
|
||||
return deprecated(f)
|
||||
return wrapper()
|
||||
|
||||
@ -66,7 +66,7 @@ def v2_auth_deprecated(f):
|
||||
what=f.__name__ + ' of the v2 Authentication APIs',
|
||||
as_of=versionutils.deprecated.MITAKA,
|
||||
in_favor_of=('a similar function in the v3 Authentication APIs'),
|
||||
remove_in=0)
|
||||
remove_in=+7)
|
||||
return deprecated(f)
|
||||
return wrapper()
|
||||
|
||||
|
7
releasenotes/notes/v2-dep-d6e7ab2d08119549.yaml
Normal file
7
releasenotes/notes/v2-dep-d6e7ab2d08119549.yaml
Normal file
@ -0,0 +1,7 @@
|
||||
---
|
||||
deprecations:
|
||||
- >
|
||||
[`blueprint deprecated-as-of-pike <https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of-pike>`_]
|
||||
The v2.0 ``auth`` and ``ec2`` APIs were already maked as deprecated in the Mitaka release,
|
||||
although no removal release had yet been identified. These APIs will now be removed in the 'T' release.
|
||||
The v3 APIs should be used instead.
|
Loading…
Reference in New Issue
Block a user