Weird thing is that when I call an endpoint, only one of the
prod URLs work, and everything else doesn't. I'm confused on where to continue.
I have set a
dev and prod stage to the authorizer, but I doubt that works because the authorizer itself isn't attached to any API gateway.
There's an error, but I don't know what it means
What I noticed is that the
prod stage doesn't link to the API Gateway like the dev stage.
Okay so I found the issue, and it seems to be a bug of Claudia? When using the
set-version command, it doesn't create a proper permission policy for that stage. So, I created a command for aws command line.aws lambda add-permission --function-name FUNCTION:STAGE --statement-id web-api-access-STAGE-TIMESTAMP --action lambda:InvokeFunction --principal apigateway.amazonaws.com --source-arn arn:aws:execute-api:REGION:ACCOUNT_ID:API_ID/authorizers/\*
so you can't set the version to an alias that's never been deployed before; you need to use
claudia update at least once for that alias
or
claudia create to set it initially
after, that, you can use
set-version to reassign a deployed alias
Hey folks,
I can't see anywhere if there is an argument to switch yarn instead of npm. I am using
I can't see anywhere if there is an argument to switch yarn instead of npm. I am using
yarn workspaces and try to create a lambda function from a project which depends on another local package in monorepo. npm --production fails to recognize local packages so yarn support would be life saver
When I use the files property in packages.json, claudia is not finding the /var directory. This is the temp directory the package is compiled in. Note, I'm on a mac
Hello!
I'm trying to implement URL redirection on a GET endpoint similar to the example here (https://github.com/claudiajs/example-projects/blob/master/web-serving-html/web.js).
The example:
// because the success code is 3xx, the content will be used as the redirect location
api.get('/redirect', function () {
'use strict';
return 'https://github.com/claudiajs/claudia';
}, { success: 302 });My code :
const APIBuilder = require('claudia-api-builder');
const API = new APIBuilder();
API.get('/token', request => myFunction(API, request), {
success: constants.statusCodes.movedTemporarily, // this is 307
});I've tested it on a browser and the page does not get redirected. The redirection URL simply gets outputted onto the page itself. Any idea on what I may be misunderstanding?
Hello! I use Claudia API Builder together with AWS API Gateway and now I decided to switch some API to AWS ALB (due to 30 sec limitation of API Gateway). Is it possible (or it's planning) to support simultaneously API Gateway and ALB? It's mostly the same payload structure and it will be good to have such option.
Hello guys, I really enjoy using ClaudiaJS for lambda deployments Thanks for that.
Please, while deploying I see some logs of my App in my terminal, is ClaudiaJS running my handler somehow before pushing it to AWS (at the package validation step)? If yes is it possible to disable this?
Hi, everyone. I'm having a trouble and I dont know where it is. I created a facebook page to use claudia bot. I set a AWS account got the IAM keys. When I did the command claudia create --region us-east-1 --api-module "something" --configure-fb-bot it didnt finish. It appeared a 400 connection code. But the bot actually worked on facebook. The problem is that because the create didn't finish now I can't update it. When I try to run the same command again it shows that somewhere (I dont know where) has a configuration with restriction of running it again (something like repeatable: false)
Hello, we would like to build a slack bot that will call an AWS lambda function. We're only interested in slack as the messaging platform. Is there a way to prune the claudia-bot-builder's dependencies. Claudia-bot-builder is 45mb on my windows machine. We would like to avoid packaging dependencies for other platforms alexa,facebook etc. Is this possible?
I guess looking at node_modules folder size may not be the right way. This says bundle size is 77.9kb. https://bundlephobia.com/result?p=claudia-bot-builder@4.5.0
Are there any examples of using claudia-bot-builder with SAM lambda function. Copying the code example from https://github.com/claudiajs/example-projects/blob/master/slack-delayed-response/bot.js into /src/handlers/index.js file in a SAM application and in the template.yml file setting the Handler to ./src/handlers/index.api did not work.
1 reply
@VinodhThiagarajan1309 This looks promising but I havent pulled it in and tested - https://github.com/chongzixin/express-swagger-claudia
I guess you need to delete old versions of your function(s).
There are many scripts for that, and you can also use some SAR app (such as this one: https://lumigo.io/blog/a-serverless-application-to-clean-up-old-deployment-packages/)
There are many scripts for that, and you can also use some SAR app (such as this one: https://lumigo.io/blog/a-serverless-application-to-clean-up-old-deployment-packages/)
Check this for more info: https://epsagon.com/tools/free-lambda-code-storage-exceeded/
Hey - I just updated a lambda function and ran "claudia set-cloudfront-trigger ..." with the newly created version. This used to run nicely. However I just started getting the message " You cannot update the specified distribution using this API version because it is associated with a cache policy." When I set the version back to an older one it works. Has something changed in AWS? Looking at the "Cache Policy Name:" on my CF distribution shows blank. Any ideas anyone?
hi everyone. new here. was wondering if anyone had experience tree-shaking their application using claudia? the limitation i am hitting is
claudia update seems to basically require node_modules to have all your modules in the lambda zip file, which effectively renders tree-shaking useless
i've been running into issues trying to get webpack to bundle and then upload that bundled file. most of my errors are coming from the validate package step
You can skip re-installing node modules by adding the
Also, if you have tree shaking, you probably use Webpack or something similar. In that case, you don’t want to deploy the source. You want to deploy the build instead. Claudia requires the package.json file and Claudia config. I guess you can copy a package.json file without dependencies and Claudia config file to your build folder before the deployment, and then run the Claudia update command.
--use-local-dependencies flag. That will use your local dependencies instead of doing the re-install.Also, if you have tree shaking, you probably use Webpack or something similar. In that case, you don’t want to deploy the source. You want to deploy the build instead. Claudia requires the package.json file and Claudia config. I guess you can copy a package.json file without dependencies and Claudia config file to your build folder before the deployment, and then run the Claudia update command.
error
v12.16.2
thats my node version
while calling