Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions column no longer shows AWS S3 permissions #9730

Closed
cyberduck opened this issue Oct 11, 2016 · 7 comments
Closed

Permissions column no longer shows AWS S3 permissions #9730

cyberduck opened this issue Oct 11, 2016 · 7 comments
Assignees
Labels
enhancement s3 wontfix

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Oct 11, 2016

6ad5feb created the issue

A year or two ago, you helpfully implemented a suggestion of mine (emailed to dkocher@cyberduck.io on Thu, Jun 12, 2014 at 6:08 PM, subject "s3.amazonaws.com and permission column") of showing AWS permissions in the permissions column, but since 5.1 or so, this seems to have stopped working; the permissions column has gone back to just showing "--". This may be related to another issue #9731 I've been newly seeing (in a file's info dialog, changes to permission are not immediately shown without refresh + returning to that file's info dialog), but I'll of course enter a separate ticket for that one.

For reference (I don't recall if I created a tracker account and entered it as a ticket, though I see in my email David Kocher replied suggested I do so), this was the original email back then:

At https://groups.google.com/forum/#!msg/cyberduck/kJqa9boQDLY/482b1UD4yLwJ you stated that

"Because the ACL is a list of grantees with a list of permissions it is difficult to visualize in a single table cell. I understand that you suggest just to display the permissions of the "http://acs.amazonaws.com/groups/global/AllUsers" (anonymous) group. We would need to introduce a new column in the browser for this which I will consider for a future release."

You wouldn't necessarily need a new column, and you wouldn't have to show just the permissions for the anonymous group. Since the permission column isn't currently being used to display anything else while connected to s3, then for Amazon s3 connection cases alone, each cell in the Permission column could display full permission information for that row's file, as a simple comma-delimited or semicolon-delimited string, e.g. "Everyone:READ; exampleuser:FULL_CONTR..." Sure, depending on the number of grantees, that may seem a bit long for one table cell, but the user could always just drag the column boundary to widen the column until there's no ellipsis and see the whole grantee list.

Thanks.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 17, 2016

@dkocher commented

Table cell values are cached. Therefore values are not displayed after the ACLs are retrieved when the Info panel is opened for a file. 

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 19, 2016

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 19, 2016

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 11, 2017

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 11, 2017

@dkocher commented

Ticket retargeted after milestone closed

1 similar comment
@cyberduck
Copy link
Collaborator Author

cyberduck commented May 5, 2017

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2017

@dkocher commented

We are unable to fix this without a severe performance impact as reading the ACLs requires another HTTP request for every file.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement s3 wontfix
Projects
None yet
Development

No branches or pull requests

2 participants