-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
self_assume_role var.role_name is null #282
Comments
modified the module a bit
used this module generated the following policy
but the errored out with
|
the policy does not take |
speaking with aws support, i'm told:
|
guess we need to open a ticket with the aws provider to handle this logic change |
further discussion with aws support, this is a proposed solution.
this one at least is valid. |
we confirmed that the conditional policy works for us. |
This issue has been resolved in version 5.5.2 🎉 |
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. |
Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the
examples/*
directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by runningterraform init && terraform apply
without any further changes.If your request is for a new feature, please use the
Feature request
template.Versions
Module version [Required]: v5.5
Terraform version:
terraform -v
Terraform v1.2.9
on darwin_arm64
Reproduction Code [Required]
Expected behavior
for a role to be created
Actual behavior
Additional context
related to #281
cc @bryantbiggs
The text was updated successfully, but these errors were encountered: