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

Google group access to persistent buckets #4281

Closed
jnywong opened this issue Jun 25, 2024 · 4 comments
Closed

Google group access to persistent buckets #4281

jnywong opened this issue Jun 25, 2024 · 4 comments

Comments

@jnywong
Copy link
Member

jnywong commented Jun 25, 2024

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)

@consideRatio consideRatio self-assigned this Jun 25, 2024
@consideRatio
Copy link
Contributor

https://infrastructure.2i2c.org/howto/features/buckets/#allowing-authenticated-access-to-buckets-from-outside-the-jupyterhub

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.

@jnywong
Copy link
Member Author

jnywong commented Jun 25, 2024

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.

@jnywong
Copy link
Member Author

jnywong commented Jul 1, 2024

We have established that serviceusage.services.use project permissions are required to allow application default credentials (ADC) to be recognized.

  • @consideRatio to update the Infrastructure Docs with note on serviceusage.services.use

@jnywong
Copy link
Member Author

jnywong commented Jul 1, 2024

@jnywong jnywong closed this as completed Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants