feat: Add an AMI version output to modules/eks-managed-node-group #3243
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
Adds an output to the
eks-managed-node-groupmodule with the release version used for the node group.Motivation and Context
The release version being used (when not supplied from the outside with the
ami_release_versionorami_idvariables) is only available in a resource and locals private to this module. Users of the module can therefore not determine what AMI release version is being used if they useuse_latest_ami_release_version; this change adds an output with that information, which makes it possible for users of the module to determine whether an update is happening (by comparing to anaws_eks_managed_node_groupdata resource, for example).Breaking Changes
No, this only adds an output and makes no breaking changes.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectsThe existing
examples/eks-managed-node-groupapplies with no changes in the plan after this commit. The examples do not seem to include examples of using the outputs of the module, and I did not add one.pre-commit run -aon my pull request