Deprecated Functionality (Juno Edition)
This is a blueprint to track the deprecation of classes, methods, functions, features, etc during the Juno development cycle. Items attached to this BP should (if at all possible) still be available until at least the start of development for K. Any class, method, etc marked as deprecated will use the @deprecated decorator to indicate it's status.
Items open for deprecation in Juno:
- (jamielennox) Federation extension endpoints, per https:/
- /v3/OS-
- /v3/OS-
- (ayoung) support for method-name = <auth-plugin> in keystone.conf (already deprecated, but not formally); remove reliance on deprecated method in tests
- (morganfainberg) token_api
- (henrynash) increase verbosity of KVS deprecations, and bump them for removal in kilo rather than juno
Blueprint information
- Status:
- Complete
- Approver:
- Keystone Drivers
- Priority:
- Low
- Drafter:
- Morgan Fainberg
- Direction:
- Approved
- Assignee:
- Keystone Drivers
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Dolph Mathews
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
Is it worth tracking proposals with keystone-specs somehow?
It'd be great to have that documentation. Each deprecation would have it's own impact, etc. -Dolph
Gerrit topic: https:/
Addressed by: https:/
Mark methods on token_api deprecated
Gerrit topic: https:/
Addressed by: https:/
Do not load auth plugins by class in tests
Addressed by: https:/
Mark kvs backends as deprecated, for removal in Kilo.
Addressed by: https:/
Mark the trust kvs backend deprecated, for removal in Kilo
Addressed by: https:/
Mark the revoke kvs backend deprecated, for removal in Kilo
