-
Notifications
You must be signed in to change notification settings - Fork 20
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
ack apigateway role_policies default #51
Comments
This issue has been automatically marked as stale because it has been open 30 days |
Hi @oscarboher, I cannot reproduce this, using the example works as expected. One thing I noticed is that the apigatewayv2 controller latest version is |
@oscarboher, if you are still experiencing this, please re-open and provide more detail how to reproduce. |
Description
Trying to customize apigatewayv2 helm installation and irsa role creation with minimal configuration fails on the IRSA role_policies as the lookup default value does not match the key type.
The default is an object {} while the map element role_policies is not defined afaik.
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.Versions
Module version: 2.2.0
Terraform version: 1.6.6
Provider version(s):
Reproduction Code [Required]
main.tf:
apigatewayv2 variable:
Steps to reproduce the behavior:
terraform plan (with valid variables for eks cluster required vars)
Expected behavior
Helm chart is installed using chart_version, and IRSA role is created with default policies
Actual behavior
Terraform plan fails as the lookup for role policies for apigatewayv2 default return does not match the role_policies key type
Terminal Output Screenshot(s)
Additional context
The text was updated successfully, but these errors were encountered: