Skip to content
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

fix(autoscaling): move lifecycle hook targets to their own module #2628

Merged
merged 12 commits into from
May 28, 2019

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented May 24, 2019

In accordance with new guidelines, we're centralizing cross-service
integrations into their own package. In this case, centralizing
AutoScaling Lifecycle Hook Targets into
@aws-cdk/aws-autoscaling-hooktargets.

Fixes #2447.

BREAKING CHANGE: using a Topic, Queue or Lambda as Lifecycle Hook
Target now requires an integration
object from the @aws-cdk/aws-autoscaling-hooktargets package.


Pull Request Checklist

  • Testing
    • Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
    • CLI change?: coordinate update of integration tests with team
    • cdk-init template change?: coordinated update of integration tests with team
  • Docs
    • jsdocs: All public APIs documented
    • README: README and/or documentation topic updated
    • Design: For significant features, design document added to design folder
  • Title and Description
    • Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
    • Title: use lower-case and doesn't end with a period
    • Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
    • Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"
  • Sensitive Modules (requires 2 PR approvers)
    • IAM Policy Document (in @aws-cdk/aws-iam)
    • EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
    • Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

In accordance with new guidelines, we're centralizing cross-service
integrations into their own package. In this case, centralizing
AutoScaling Lifecycle Hook Targets into
`@aws-cdk/aws-autoscaling-hooktargets`.

Fixes #2447.

BREAKING CHANGE: using a Topic, Queue or Lambda as Lifecycle Hook
Target now requires an integration
object from the `@aws-cdk/aws-autoscaling-hooktargets` package.
@rix0rrr rix0rrr requested review from SoManyHs and a team as code owners May 24, 2019 08:32
@@ -1,5 +1,3 @@
lambda/bundle.zip
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we leave this package for another version as we deprecate it?

constructor(private readonly fn: lambda.IFunction) {
}

public bind(lifecycleHook: autoscaling.ILifecycleHook): autoscaling.LifecycleHookTargetProps {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if bind should pass a scope: Construct (sounds like a useful pattern in general).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

aws-autoscaling-hooks
3 participants