For certain built AMIs, we need to only optionally add components. For example, with a managed Red Hat Linux AMI, it does not come with the aws cli preinstalled. However, Amazon Linux 2 does. Because the component configuration is an ordered instantiation of blocks, you can't define this conditional functionality.
What then happens is the RHEL AMI installs aws cli version 2 correctly, but the Amazon Linux one tries to make a duplicate install, which breaks usage of it (since it does not uninstall first).
Would be super awesome if the component block was a list of arns instead of how it stands today!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
For certain built AMIs, we need to only optionally add components. For example, with a managed Red Hat Linux AMI, it does not come with the
aws
cli preinstalled. However, Amazon Linux 2 does. Because the component configuration is an ordered instantiation of blocks, you can't define this conditional functionality.What then happens is the RHEL AMI installs aws cli version 2 correctly, but the Amazon Linux one tries to make a duplicate install, which breaks usage of it (since it does not uninstall first).
Would be super awesome if the
component
block was a list of arns instead of how it stands today!Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
References
No response
Would you like to implement a fix?
None