-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Description
What is the problem?
LambdaInvokeAction does not accept region as a parameter. I have a CodePipeline that needs to invoke a function in a different region. I was hitting errors due to the LambdaInvokeAction assuming the region is the same as the CodePipeline, but it worked when I manually set the region in the action configuration in the AWS console. According to the documentation this property can be defined in Cloudformation so it’s not clear why it’s not supported in CDK. I noticed that LambdaInvokeActionProps extends the CommonActionProps interface rather than the ActionProperties interface which does include the region field.
Reproduction Steps
Created a Codepipeline stack in us-west-2 with a stage containing a LambdaInvokeAction that needed to invoke a function in us-east-1.
What did you expect to happen?
I expected to be able to define the region for the action to invoke the lambda.
What actually happened?
The action had a region of us-west-2 and I could only change the region manually in the console.
CDK CLI Version
1.108.0
Framework Version
No response
Node.js Version
14.16.1
OS
Mac OS Big Sur (11.6)
Language
Typescript
Language Version
4.5.2
Other information
No response