-
Notifications
You must be signed in to change notification settings - Fork 88
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
Existing role configuration #83
Comments
Just checked out the source code under role.py. Looks like that is not supported at the moment and we just generate whatever is "name"_"environment.profile" for the role and do the check there. i think it would be great just to make the role name configurable. would make a PR myself but i think you would have a better idea of where it fits in the config file (im still rather new to aws management stuff) |
Bump. Using an already existent role is needed. |
@woqer would you be willing to create a pull request for this functionality that you need? |
Sure thing @josegonzalez :) |
Does kappa support using existing IAM roles? (I'm assuming it does based on the kinesis sample)
I see the kinesis sample with the "iam" block but it doesn't seem to include the "environments" block.
I just get an error saying "Invalid environment dev specified"
The text was updated successfully, but these errors were encountered: