generated from aws-ia/terraform-repo-template
-
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
Invalid index
error when emrcontainers or step functions (sfn) are not enabled
#43
Closed
1 task done
Labels
bug
Something isn't working
Comments
bdellegrazie
added a commit
to bdellegrazie/terraform-aws-eks-ack-addons
that referenced
this issue
Jul 5, 2023
When emrcontainers or step function capabilties were disabled, Terraform would try to assign the associated policy. The policy doesn't exist because that component is disabled. fixes: aws-ia#43
bdellegrazie
added a commit
to bdellegrazie/terraform-aws-eks-ack-addons
that referenced
this issue
Jul 5, 2023
When emrcontainers or step function capabilties were disabled, Terraform would try to assign the associated policy. The policy doesn't exist because that component is disabled. As a test, an all controllers disabled module has been added to the example. fixes: aws-ia#43
bdellegrazie
added a commit
to bdellegrazie/terraform-aws-eks-ack-addons
that referenced
this issue
Jul 5, 2023
When emrcontainers or step function capabilties were disabled, Terraform would try to assign the associated policy. The policy doesn't exist because that component is disabled. As a test, an all controllers disabled module has been added to the example. fixes: aws-ia#43
bdellegrazie
added a commit
to bdellegrazie/terraform-aws-eks-ack-addons
that referenced
this issue
Jul 5, 2023
When emrcontainers or step function capabilties were disabled, Terraform would try to assign the associated policy. The policy doesn't exist because that component is disabled. As a test, an all controllers disabled module has been added to the example. fixes: aws-ia#43
bdellegrazie
added a commit
to bdellegrazie/terraform-aws-eks-ack-addons
that referenced
this issue
Jul 5, 2023
When emrcontainers or step function capabilties were disabled, Terraform would try to assign the associated policy. The policy doesn't exist because that component is disabled. As a test, an all controllers disabled module has been added to the example. fixes: aws-ia#43
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
If, using the existing example, you disable the emrcontainers and/or step functions as follows:
Then terraform responds with the following output:
This is always reproducible with v2.0.0 of the provider (latest at time of writing)
Versions
Module version: v2.0.0
Terraform version: 1.5.2
Provider version(s):
Reproduction Code
See example above in the description.
This is verifiable with the example code in this repository.
Expected behavior
Resources to be provisioned
Actual behavior
Error reported as above.
Terminal Output Screenshot(s)
Error reported as above.
Additional context
I believe this can easily be solved by either a conditional assignment:
(e.g.)
or by the use of
try
:The text was updated successfully, but these errors were encountered: