This repository was archived by the owner on Dec 20, 2025. It is now read-only.
fix(aws): Launch template version of ASG default to '$Latest' when not defined (backport #6373)#6375
Merged
mergify[bot] merged 1 commit intorelease-1.37.xfrom May 15, 2025
Conversation
jasonmcintosh
approved these changes
May 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
An edge case involves an ASG created via CloudFormation or via a Crossplane custom resource which the launchTemplate.version not defined. According to the AWS docs this defaults to $Latest as it is not a mandatory field.
When Clouddriver caches it and if it matches an Application name it will be present in the Cluster view tab. This causes an NPE on the ServerGroupController as:
This is an automatic backport of pull request #6373 done by [Mergify](https://mergify.com).