fix(scheduler-alpha): remove targetOverrides prop from Schedule

[samson-keung]

Issue # (if applicable)

Tracking: #31785

Reason for this change

The targetOverrides prop is adding confusion to the API as it override what is set on the target. A better way to reuse target props would be:

const targetBaseProps = { input: ...someInput... }

const schedule1 = new Schedule(this, 'Schedule', {
    scheduleExpression: ScheduleExpression.cron({ day: '20' }),
    target: new targets.LambdaInvoke(props.func, {
        ...targetBaseProps,
        // override whatever or not to override
        }),
    }),
});

Description of changes

Removed targetOverrides prop and the related tests. Also updated the integ test which was using the prop.

Description of how you validated changes

Removing a prop so n/a.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

---

BREAKING CHANGE: This PR removes the targetOverrides prop from the Schedule construct.

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[gracelu0]

Do we mean to remove this key property as part of this change?

[samson-keung]

Yes. Removing it from the interface as it is not being used currently. I would like to start with minimal exposed APIs, then we can add more in the future if needed.

[gracelu0]

Do we know if this is a common use case? If so it may be worth keeping this README section with your updated suggestion for overriding target props

[samson-keung]

I don't think this is common use case. If we see the need in the future, we can add.

[gracelu0]

LGTM!

[mergify]

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 CodeBuild CI Report

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

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

[mergify]

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).

[github-actions]

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.