Move s3_token middleware to keystoneclient

Registered by Brant Knudson on 2014-01-27

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:
milestone icon 2014.1
Started by
Brant Knudson on 2014-02-06
Completed by
Dolph Mathews on 2014-02-11

Related branches

Sprints

Whiteboard

Is there something tracking this effort on the keystoneclient side? (partial overlap with https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of-icehouse )

Created a blueprint in python-keystoneclient: https://blueprints.launchpad.net/python-keystoneclient/+spec/s3-token-to-keystoneclient

Gerrit topic: https://review.openstack.org/#q,topic:bug/1270909,n,z

Addressed by: https://review.openstack.org/70240 (merged)
    Update requirements to 661e6

Addressed by: https://review.openstack.org/71690 (merged)
    Deprecate s3_token middleware

Gerrit topic: https://review.openstack.org/#q,topic:bp/s3-token-to-keystoneclient,n,z

Addressed by: https://review.openstack.org/73370 <-- this is a follow up bug fix, not part of the impl
    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-keystoneclient and deprecate: INPROGRESS

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.