Closed Tristano8 closed 1 month ago
In your function definition
MyFunction:
EventInvokeConfig:
DestinationConfig:
OnFailure:
Destination': !GetAtt ErrorReporterFunction.Arn
Type: 'Lambda'
Properties:
AutoPublishAlias: 'Live'
CodeUri: 'other-bootstrap-file'
FunctionName:
'Fn::Sub': "${AWS::StackName}-my-lambda"
Handler: 'UNUSED'
LoggingConfig:
ApplicationLogLevel: 'DEBUG'
LogFormat: 'JSON'
SystemLogLevel:
Fn::FindInMap:
- LambdaLogLevel
- Ref: 'LogSeverity'
- System
MemorySize: 512
Policies:
- 'AWSLambdaBasicExecutionRole'
Runtime: 'provided.al2'
Timeout: 300
Type: 'AWS::Serverless::Function'
I believe you accidentally defined EventInvokeConfig
outside of the properties. According to documentation, it should be under Properties
Going to mark this issue as resolved. Feel free to open a new issue if it doesn't fix it and we're happy to help.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one.
Description
Using an EventInvokeConfig results in a processed template that ignores these fields completely
Steps to reproduce
Deploy something like the following template:
Observed result
The processed template after deployment looks something like the following for MyFunction:
No reference to the EventInvokeConfig exist anywhere in the processed template.
Deploying the following as a top level resource seems to work:
Expected result
The transform should include my declared EventInvokeConfig in the processed template
Additional environment details
sam --version
: