You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes ✅: please list the AWS provider version which introduced this functionality
The feature is present in hashicorp/aws since before v4.0.0 which is the minimum version already required by this module.
Is your request related to a problem? Please describe.
Currently the iam-group-with-assumable-roles-policy puts all its groups and policies in the default IAM path (that is: /), it would be nice to have the possibility to specify a custom path.
Describe the solution you'd like.
A new path input variable to specify the path for the IAM group and IAM policy
Describe alternatives you've considered.
Having everything in the root path would break our current practices
Additional context
Pull request is coming 👍
The text was updated successfully, but these errors were encountered:
lesinigo
added a commit
to lesinigo/terraform-aws-iam
that referenced
this issue
Mar 9, 2023
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 new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.
The feature is present in
hashicorp/aws
since before v4.0.0 which is the minimum version already required by this module.Is your request related to a problem? Please describe.
Currently the
iam-group-with-assumable-roles-policy
puts all its groups and policies in the default IAM path (that is:/
), it would be nice to have the possibility to specify a custom path.Describe the solution you'd like.
A new
path
input variable to specify the path for the IAM group and IAM policyDescribe alternatives you've considered.
Having everything in the root path would break our current practices
Additional context
Pull request is coming 👍
The text was updated successfully, but these errors were encountered: