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
Projects with an access policy won't display gsutil
command
#2202
Comments
As far as I know, we don't have a local database of who has permission to access restricted Google Cloud buckets. The only way to know who has access is to ask Google. If you visit one of those restricted projects, you should see something that says "click here to request access to the Google Cloud bucket", and if you click that link, it should add you to the access list, and then send you instructions by email. There are a lot of problems with this, but this is where we are currently. |
@bemoody , I believe the part you mention is working as expected. However, once the user is added to the access list and they return to the project page they will still see something like this "Request access to the files using the Google Cloud Storage Browser. Login with a Google account is required." as if they weren't added. However, if they click on the Google Cloud Storage Bucket link at this point they will be shown the files in the bucket. Of course, we expect a different message with a |
Sorry, I replied in a hurry and should have been more clear.
I agree that would be preferable. But since we don't keep a copy of the access list, we have no idea whether the current user is on the access list or not. So we have never supported what you're describing. |
Thanks to @elfeto for pointing out this issue. Projects that are attached to a GCP bucket and have an access policy won't display the
gsutil
command for downloading the files. Here is some relevant code:The
won't get run since the project has an
access_policy
.It will eventually go to:
{% include "project/published_project_data_access.html" %}
, which will always show:The text was updated successfully, but these errors were encountered: