When publishing the lambdas using our ${service}-${stage}-${lambda} naming syntax, the newly created create_or_update_dag_metadata_handler lambda got over 64 characters and was rejected. Also, some improvements to the handler code itself.
Fixes
Lambda was renamed so that its largest automatically generated name ( hathor-explorer-service-mainnet-create_or_update_dag_metadata ) is still under this limit with 61 characters.
Improvements
Simplified the handler contract, removing the overhead of a complete ApiGateway and replacing it with the leaner InvokeHandler
Created the InvokeHandler wrapper, similar to the existing ApiGateway but with fewer parameters for direct lambda invocation instead of HTTP handling.
When publishing the lambdas using our
${service}-${stage}-${lambda}naming syntax, the newly createdcreate_or_update_dag_metadata_handlerlambda got over 64 characters and was rejected. Also, some improvements to the handler code itself.Fixes
hathor-explorer-service-mainnet-create_or_update_dag_metadata) is still under this limit with 61 characters.Improvements
ApiGatewayand replacing it with the leanerInvokeHandlerInvokeHandlerwrapper, similar to the existingApiGatewaybut with fewer parameters for direct lambda invocation instead of HTTP handling.