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

chore(scheduler-alpha): unit test schedule with Lambda version as target #31872

Merged
merged 2 commits into from
Oct 24, 2024

Conversation

samson-keung
Copy link
Contributor

@samson-keung samson-keung commented Oct 24, 2024

Issue # (if applicable)

Tracking #31785.

Reason for this change

Missing this test case.

Description of changes

Adding a unit test to verify Schedule works with Lambda Version and correct permissions are added.

Description of how you validated changes

Unit test.

Checklist


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

@github-actions github-actions bot added the p2 label Oct 24, 2024
@aws-cdk-automation aws-cdk-automation requested a review from a team October 24, 2024 06:05
@samson-keung samson-keung marked this pull request as ready for review October 24, 2024 06:05
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Oct 24, 2024
@aws-cdk-automation aws-cdk-automation added the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Oct 24, 2024
Copy link
Contributor

@kaizencc kaizencc left a comment

Choose a reason for hiding this comment

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

Approving this PR but hoping that you take the time to fix the other thing I've flagged while this module is still in alpha

const lambdaVersion = new lambda.Version(stack, 'MyLambdaVersion', {
lambda: func,
});
const lambdaTarget = new LambdaInvoke(lambdaVersion, {});
Copy link
Contributor

Choose a reason for hiding this comment

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

nothing to do with your PR, but since LambdaInvoke can be valid with no properties, we should allow the second field to be optional so we can write LambdaInvoke(lambdaVersion). As simple as:

  constructor(
    func: lambda.IFunction,
    props: ScheduleTargetBaseProps = {},
  ) {

Copy link
Contributor

mergify bot commented Oct 24, 2024

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation aws-cdk-automation removed the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Oct 24, 2024
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 45b2057
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit 6136d9e into aws:main Oct 24, 2024
15 checks passed
Copy link
Contributor

mergify bot commented Oct 24, 2024

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 24, 2024
@samson-keung samson-keung deleted the scheduler-unit-test-lambda-version branch October 28, 2024 18:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
contribution/core This is a PR that came from AWS. p2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants