s3 ACL Grantee class is missing support for by-email and by-uri
Bug #919538 reported by
DreamHost
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
txAWS |
Fix Released
|
Medium
|
Duncan McGreggor |
Bug Description
See the docs here:
http://
Only the first option for Grantee values is implemented in txAWS.
Related branches
lp:~oubiwann/txaws/919538-grantee-email-uri
- Thomas Herve: Approve
-
Diff: 93 lines (+53/-7)2 files modifiedtxaws/s3/acls.py (+25/-6)
txaws/s3/tests/test_acls.py (+28/-1)
Changed in txaws: | |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in txaws: | |
milestone: | none → 0.3 |
Changed in txaws: | |
status: | In Progress → Fix Committed |
Changed in txaws: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think that defining a Grantee by URI might be required in order to support canned ACLs, for instance, "public-read," since under the hood, the canned ACL for public read does this:
<Grant> www.w3. org/2001/ XMLSchema- instance" xsi:type="Group"> acs.amazonaws. com/groups/ global/ AllUsers</URI> Permission> READ</Permissio n>
<Grantee xmlns:xsi="http://
<URI>http://
</Grantee>
<
</Grant>