{
"devDependencies": {
"claudia": "^5.13.1"
},
"dependencies": {
"claudia-api-builder": "^4.1.2"
}
}
when I tried with callbackWaitsForEmptyEventLoop=false
,
var ApiBuilder = require('claudia-api-builder'),
api = new ApiBuilder();
module.exports = api;
api.any('/test', function (request) {
request.lambdaContext.callbackWaitsForEmptyEventLoop = false;
var prefix = request.proxyRequest.queryStringParameters.id;
console.log('hello: ' + prefix);
setTimeout(function () {
console.log('after timeout: ' + prefix);
}, 5000);
return new ApiBuilder.ApiResponse('OK ' + prefix, {'X-Version': '202', 'Content-Type': 'text/plain'}, 200);
});
I got 'after timeout' but only when I sent two request (19 sec between each)
ResourceConflictException: The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:…
, which suddenly started happening, after a 150 successful claudia update
s by CI? See claudiajs/claudia#226.
authorizationType: 'AWS_IAM'
equivalent with --deploy-proxy-api
Does anyone know if the lambda functions deployed using Claudia face any issues while updating due to the latest states rollout or is already taken care of?
Context:
All AWS CLIs and SDKs have supported monitoring Lambda function states transitions since the original announcement in 2019. Infrastructure as code tools such as AWS CloudFormation, AWS SAM, Serverless Framework, Hashicorp Terraform (>=2.40.0), and Cloud Custodian (>=0.9.14.0) also already support states. Customers using these tools do not need to take any action as part of this, except for one recommended service role policy change for AWS CloudFormation customers (see Updating CloudFormation’s service role below).
However, there are some customers using SDK-based automation workflows or calling Lambda’s service APIs directly, that must update those workflows for this change. To allow time for testing this change, we are rolling it out in a phased model, much like the initial rollout for VPC attached functions. We encourage all customers to take this opportunity to move to the latest SDKs and tools available.
Reference: https://aws.amazon.com/blogs/compute/coming-soon-expansion-of-aws-lambda-states-to-all-functions/
Hi
I need one urgent solution on one issue.
I have converted my entire nodejs project to aws lambda using this claudia.
Everything look gook. but while sending base64 content which is arround 500KB, giving me payloadTooLarge error.
While running service it workd fine...but aws is not allowing me to send this request.
What should be the fix?
is aws lambda function created by claudia synchronous or async?
Hi
I am facing issue with claudia update comment
When I run update command it proceeds and after 'validating package' statement it start to print garbage on my terminal.
title
I have attached the image and this goes on, and never terminate until I terminate the command
It is working 10 days back