(lambda): Imported functions don't have account & region set correctly

[MarkRobbo]

What is the problem?

Importing a lambda function from ARN using fromFunctionArn does not result in the correct region and account being used from the ARN.

Looking at the code this is a similar bug to #11199, environmentFromArn is not provided in the Import

Reproduction Steps

Either

const lambda = LambdaFunction.fromFunctionAttributes(this, 'ImportedFunction', {
  functionArn: 'arn:aws:lambda:us-east-1:123456789012:function:ProcessKinesisRecords',
  sameEnvironment: false
});

or

const lambda = this.cfnStackSafetyActionFunction = LambdaFunction.fromFunctionArn(
  this,
  'ImportedFunction',
  'arn:aws:lambda:us-east-1:123456789012:function:ProcessKinesisRecords'
);

What did you expect to happen?

Expected lambda.env.region === 'us-east-1' and lambda.env.account === '123456789012'

What actually happened?

lambda.env == scope.env

The environment details are derived from the stack environment rather than the provided ARN, preventing activities like a Lambda Invoke action to a different region in the same account as the CloudFormation Region always points to the same account.

CDK CLI Version

1.128.0 (build 1d3883a)

Framework Version

No response

Node.js Version

v16.7.0

OS

Amazon Linux

Language

Typescript

Language Version

No response

Other information

No response

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.