fix: Set image_id
to come from the launch template instead of data source for self-managed node groups
#2239
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.
Description
Fixes issue #2235 ; configure the output of image id to be the real output of the launch_template
Motivation and Context
#2235
Breaking Changes
If a user provided a custom ami_id and relied on the broken information this submodule was returning, they could see a change in behavior as the output corrects itself.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectsexamples/self_managed_node_group
terraform output -json | jq .self_managed_node_groups.value.bottlerocket.image_id
ami-0f2b7c6874eb8414f
(The default AMI, despite being overridden in the config)ami-04958b57e72e69fb0
(The actual bottlerocket ami id)pre-commit run -a
on my pull request