Deprecate in favour of keystoneauth
Keystoneauth is sufficiently ready that we should start using it instead of the relevant keystoneclient bits. This will involve deprecating the session, auth plugins, service catalog, access info etc components.
It turns out to be way to difficult to put a direct dependency on all these pieces from keystoneclient to keystoneauth. Instead we are just going to mark them all deprecated and expect people to switch to keystoneauth.
Blueprint information
- Status:
- Started
- Approver:
- Steve Martinelli
- Priority:
- Medium
- Drafter:
- Jamie Lennox
- Direction:
- Approved
- Assignee:
- Jamie Lennox
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
- Good progress
- Milestone target:
- None
- Started by
- Steve Martinelli
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Deprecate Session
Addressed by: https:/
Deprecate auth plugins from keystoneclient
Addressed by: https:/
Replace TestResponse with requests_mock
Addressed by: https:/
Deprecate adapter
Addressed by: https:/
Deprecate the baseclient.Client
Addressed by: https:/
Seperate Client base test class
Addressed by: https:/
Make tests run against original client and sessions