-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Start implementing setIamPolicy, getIamPolicy, and testIamPermissions #1073
Comments
@tseaver Are you planning on doing this or just added docs as a resource? |
I'm still planning on it. |
Great to hear |
@tseaver Still planning on it? |
Dropped off my radar, I'm afraid. |
Coming back on the radar or no? |
Depends on priorities, really. @jgeewax, how important would you rate this feature? |
I will tackle this issue today: it is a prerequisite for using topics as logging sink destinations (or at least for being able to script the topic setup for sink system tests). |
Good to hear. ISTM this probably belongs in |
I'm confused: those operations are about changing security settings on the API subject-domain resources (projects / topics / subscriptions.) I don't see anything related to |
I am unfamiliar with how they work so take my previous comment with a grain of salt |
These methods are basically attacking the same problem as |
Right on, @tseaver. These methods essentially API-level ACLs. |
SGTm |
I thought we already had an issue filed, must have mismembered.
See googleapis/google-cloud-node#758 and googleapis/google-cloud-node#767
@tseaver Care to take a stab at it?
The text was updated successfully, but these errors were encountered: