Skip to content
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

capacity_reservation_specification not mapped properly #1897

Closed
shupcode opened this issue Feb 23, 2022 · 3 comments · Fixed by #1979
Closed

capacity_reservation_specification not mapped properly #1897

shupcode opened this issue Feb 23, 2022 · 3 comments · Fixed by #1979

Comments

@shupcode
Copy link

Using capacity_reservation_specification in the eks managed node group or the self managed node group throws an invalid function argument:

      capacity_reservation_specification = {
        capacity_reservation_target = {
          capacity_reservation_id = aws_ec2_capacity_reservation.foobar.id
        }
      }
 Error: Invalid function argument
│ 
│   on .terraform/modules/eks/modules/eks-managed-node-group/main.tf line 99, in resource "aws_launch_template" "this":
│   99:           capacity_reservation_id = lookup(capacity_reservation_target.value, "capacity_reservation_id", null)
│     ├────────────────
│     │ capacity_reservation_target.value is "cr-xxxxxxxx"
│ 
│ Invalid value for "inputMap" parameter: lookup() requires a map as the first argument.

Fix:
A pull request has been made to flatten the nested dynamic 'capacity_reservation_target'

@github-actions
Copy link

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

@antonbabenko
Copy link
Member

This issue has been resolved in version 18.17.1 🎉

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants