During image v1 create with a location, we should ensure the location does not have any account reference

Registered by Sridevi Koushik on 2013-12-10

During image v1 create with a location, we should ensure the location does not have the account reference

Blueprint information

Status:
Started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Mark Washenberger

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/image-create-in-v1-with-location-should-validate-the-location-uri,n,z

Addressed by: https://review.openstack.org/64670
    Image create in V1 should validate the uri

Addressed by: https://review.openstack.org/34801
    Remove user and key from location in swift

Gerrit topic: https://review.openstack.org/#q,topic:bp/v1-image-create-should-validate-the-location-uri,n,z

What are scrub credentials? Are there other validation steps that are needed?
What is the priority here? Especially, I'm wondering if this is only important if we land the changes associated with removing credentials from all locations.
markwash more-info 2014-02-18

Gerrit topic: https://review.openstack.org/#q,topic:bp/remove-sensitive-data-from-locations,n,z

Thanks for the clarification
markwash wishlist 2014-03-07

The both the title and the description of this blueprint are quite misleading. Can they be updated to reflect the purpose of this blueprint?

Also, it sounds like this could be easily moved into a bug instead of having a blueprint.

Thanks
--flaper87 2014-03-10

Addressed by: https://review.openstack.org/98722
    Remove user and key from location in swift

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.