-
Notifications
You must be signed in to change notification settings - Fork 67
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
Google group access to persistent buckets #4281
Comments
It seems to be for this exact situation, I just wasn't aware - sorry for the confusion! Looking at details, it seems that there is a google group setup for access to leap as well. I figure whats needed is to verify that the access using this group procedure works all the way - and what I did may bypass your ability to test it - because you were granted permissions in another way. I think the task concretely is to tweak/verify a procedure to work against a bucket when being granted permissions via the procedure in the listed docs. |
No worries, I am glad we are getting clarity on this mechanism! That's fine, I can add a dummy test account to the Google group to test this procedure again. |
We have established that
|
Two issues opened from this work:
Closing this as complete. |
Opening a new ticket to capture the question below from a ticket that will be closed
Thanks for the explanation Erik, I will capture this insight for our Product board.
Regarding cloud permissions, do you happen to know what the Google Group @sgibson91 mentioned above is for then? Here are the relevant infrastructure docs.
Originally posted by @jnywong in #4214 (comment)
The text was updated successfully, but these errors were encountered: