Closed olivers-xaxis closed 4 months ago
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is your request related to a problem? Please describe.
Currently the policy that shows which roles a group can assume via submodule iam-group-with-assumable-roles-policy is hardcoded to match the group name. Eg given the following:
a group named
group_name
will be created, and it will have a policy calledgroup_name
which will have only one statement:That policy should have a customizable name. Eg I would want to call it "group_name_assume_roles", and someone else might want a different name. Plus it is confusing in the Policy console, you see a policy called "group_name" you think it is the main policy for that group, it is only the one for assuming roles; additional policies may end up attached to that group.
Describe the solution you'd like.
An extra optional var for the policy name, defaults to current so fully backwards compatible
Describe alternatives you've considered.
Cloning your code into our own git repo
Additional context
A PR should be straightforward but I wanted to raise this before working on it.