-
Notifications
You must be signed in to change notification settings - Fork 1
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
Permissions framework? #18
Comments
So so excited by all of this!! Here's a thought, but I haven't fully thought it through yet. I'll install this and actually get it running to think about the possibilities asap.
|
Just copying this from above with no modifications: # in each case below aws_policy_attach determines from input whether
# its a group, role, or user. And prefixes policy with `arn:aws:iam::aws:policy`
aws_group_create("testers") %>% aws_policy_attach("ReadOnlyAccess")
aws_role_create("ReadOnlyRole") %>% aws_policy_attach("ReadOnlyAccess")
aws_user_create("jane") %>% aws_policy_attach("AdministratorAccess")
# or if already created, then:
aws_role("ReadOnlyRole") %>% aws_policy_attach("ReadOnlyAccess") I really like this. What should |
right now Instead of returning whatever is returned from the paws method, we could return the updated object that the various
thoughts (when you're back)? |
I'll leave this open until we're happy with the interface for these fxns. |
@seankross Any further thoughts on the permissions fxns for now? |
Thinking about this from the perspective of this image
from the youtube video sean shared
Here's what I'm thinking:
aws_user*
/aws_users*
aws_group*
/aws_groups*
aws_role*
/aws_roles*
aws_policy*
/aws_policies*
- some of these fxns used for attaching policies to users, groups, rolesso in the end we could have a workflow like:
Another example
@seankross feedback plz
The text was updated successfully, but these errors were encountered: