Fix for LaunchConfigName nor LaunchTemplate existing on ASG object #54692
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.
SUMMARY
When attempting to use ec2_asg to make changes to an already existing autoscaling group, the module fails.
Fixes #50562
ISSUE TYPE
COMPONENT NAME
ec2_asg.py
ADDITIONAL INFORMATION
I was hiting an error when running my playbooks to modify auto-scaling groups and discovered the existing issue #50562. Taking a further look I was able to get the following error message after adding a print debug line
The print out was from the section where the error was hitting:
It turns out as evidenced by
"module_stdout": "TESTING: {u'InstanceId': 'i-007caa4fef0eeb33f', u'ProtectedFromScaleIn': False, u'AvailabilityZone': 'us-east-1d', u'HealthStatus': 'Healthy', u'LifecycleState': 'InService'}\n",
that there are in fact times where this will return without eitherLaunchConfigurationName
orLaunchTemplate
defined. (The ASG in question has a LaunchConfig).This PR adds a conditional to allow for neither to be defined and it does indeed seem to solve my issue without any unintended side-effects that I can tell.