Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 82937]
Primary programming language affected, if applicable [ID: 82936]
[ID: 82935]
[ID: 82940]
[ID: 82941]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
Problem you have encountered:
I'd be interested in a permission that can potentially accomplish the following:
`gsutil stat gs://<bucket_name>/<object_location>`
Output: <stat information>
(We're able to read object metadata here)
“storage.objects.get“ is the current permission [1] required to execute `gsutil stat gs://<bucket_name>/<object_location>`, which reads the object’s metadata. However, if this permission is granted, a user is able to execute `gsutil cat gs://<bucket_name>/<object_location>` as well, which reads the object’s data.
What you expected to happen:
Is it possible to create a new permission which allows users to read object’s metadata only?
Steps to reproduce:
1. gsutil stat gs://<bucket_name>/<object_location>
2. gsutil cat gs://<bucket_name>/<object_location>
Other information (workarounds you have tried, documentation consulted, etc):
From researching our public documentation and internal knowledge base, there do not appear to be any valid workarounds at the moment.
[1]