Move s3_token middleware to keystoneclient
The s3_token middleware will be moved from keystone to keystoneclient. Applications will still be able to import s3_token from keystone, but 1) they'll get a deprecated warning when they do it, and 2) keystone will just import * s3_token from keystoneclient.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Brant Knudson
- Direction:
- Needs approval
- Assignee:
- Brant Knudson
- Definition:
- New
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Brant Knudson
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
Is there something tracking this effort on the keystoneclient side? (partial overlap with https:/
Created a blueprint in python-
Gerrit topic: https:/
Addressed by: https:/
Update requirements to 661e6
Addressed by: https:/
Deprecate s3_token middleware
Gerrit topic: https:/
Addressed by: https:/
Remove s3_token functional tests
Work Items
Work items:
Wait for keystoneclient release with the s3_token code copy: DONE
Update requirements to 0.5.0 keystoneclient: INPROGRESS
Remove code from keystone, import from python-
Dependency tree
* Blueprints in grey have been implemented.
