fix: Add missing IMDSv2 metadata restrictions for aws launch config #1257
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Metadata Options for Launch Configuration
Description
This PR resolves issue #1113
Currently metadata options
metadata_http_endpoint
,metadata_http_tokens
andmetadata_http_put_response_hop_limit
are supported foraws_launch_templates
with #938 but not foraws_launch_configuration
as it has arrived later to AWS provider on hashicorp/terraform-provider-aws#14637. This PR adds settings for IDMS v2 restrictions to aws_launch_configuration.Checklist