You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use this package for lambda@edge scenario. However, I get wrong CFN output fields (ap-northeast-1) after deployments for changed lambda code (us-east-1). Every time I modified lambda code in us-east-1 stack, the stack in ap-northeast-1 can not aware the changed.
You can see the two stack outputs below. NumLambdaEdgeStack.LambdaFuncArn (v4) and NumCloudfrontStack.OutputLambdaFuncArn (v2) should be the same.
I use this package for lambda@edge scenario. However, I get wrong CFN output fields (ap-northeast-1) after deployments for changed lambda code (us-east-1). Every time I modified lambda code in us-east-1 stack, the stack in ap-northeast-1 can not aware the changed.
You can see the two stack outputs below. NumLambdaEdgeStack.LambdaFuncArn (v4) and NumCloudfrontStack.OutputLambdaFuncArn (v2) should be the same.
Below is my code.
The text was updated successfully, but these errors were encountered: