fix(scheduler-targets-alpha): imported lambda function as schedule target throws synth error

[samson-keung]

Issue # (if applicable)

Closes #29284.

Reason for this change

Removed the same env check between the Schedule and the Lambda target to allow use of imported Lambda function as target.

Description of changes

Removed the check that forces the Schedule and the Lambda function to be in the same account and region.

Description of how you validated changes

• Unit test added to ensure no synth error when using imported Lambda function.
• Integ test added to ensure imported function works. The test ensures the lambda is executed and did what it is supposed to do (i.e. added tag to itself).

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

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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

[GavinZZ]

While this would fix the problem mentioned in the issue, I don't think this is a good fix in general since it removes check even for functions and scheduler with known account & regions.

[samson-keung]

That is correct. The reasoning to remove the check is explained here.

[gracelu0]

What is the deployment behaviour now without this validation if the account/region don't match? Is there any documentation on this restriction? I wasn't able to find anything.

[samson-keung]

What is the deployment behaviour now without this validation if the account/region don't match? Is there any documentation on this restriction? I wasn't able to find anything.

From my testing, different account works (although not explicitly documented). Different region will throw error at template deploy time.