-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(aws-ec2): userdata cfn-signal signal resource which is different than the attached resource #16264
Conversation
…e attached resource
@njlynch, I've fixed the merging conflict with master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
Pull request has been modified.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
… than the attached resource (aws#16264) When using `cfn-init` in EC2 UserData with a LaunchTemplate and an AutoScalingGroup the attached resource (used with `cfn-init`) is the LaunchTemplate but the signal (`cfn-signal`) should call the AutoScalingGroup. `CloudFormationInit::attach` method supports only a single resource for both init and signal - blocking the usage of LaunchTemplate and AutoScalingGroup scenario. The commit avoids a breaking change in the function signature, by adding an optional `signalResource` to the `AttachInitOptions` parameters argument ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
When using
cfn-init
in EC2 UserData with a LaunchTemplate and an AutoScalingGroup the attached resource (used withcfn-init
) is the LaunchTemplate but the signal (cfn-signal
) should call the AutoScalingGroup.CloudFormationInit::attach
method supports only a single resource for both init and signal - blocking the usage of LaunchTemplate and AutoScalingGroup scenario.The commit avoids a breaking change in the function signature, by adding an optional
signalResource
to theAttachInitOptions
parameters argumentBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license