For support requests please search or create posts on Serverless Forum: https://forum.serverless.com
Hi! I'm noticing that some devdependencies are not being excluded from our package. As an example, I see eslint in the node_modules dir of the package, but that definitely is configured as a devdependency in our package.json files. I'm sure I'm doing something wrong - does anybody have a recommendation into how I can get more insight into the way that serverless excludes dev dependencies?
Just as further information. If I open the package dir and unzip the code and run npm ls, I see a large number of extranious packages. I can confirm that these packages are 1. in the node_modules dir 2. not specified by the package.json file as dependencies 3. not required for execution of my application.
(serverless package --package out && cd out && unzip myservice.zip && npm ls)
I'm going to try to manually remove these and create the zip, then deploy that
Hi guys, I'm trying to run a mono repo serverless app locally with serverless-offline, since secrets are fetched from aws secrets manager, I can't assign $self in local runs with serverless offline, is there away to overwrite the variables fetched from ssm with .env variables on the fly without the need to rewrite my serverless.yml files?
I have a fairly key bug: https://forum.serverless.com/t/aws-flask-http-not-working-with-custom-domain-in-a-way-that-is-compatible-with-new-deployments/16935 Or maybe I've severely underestiamted % of people using serverless with custom domains
Hi! We're trying to migrate from the v2 variable resolvers to the new v3 variable resolver engine. I'm struggling with how to return "undefined" values (i.e. my resolver can't resolve).
If I return { value: undefined }, serverless gives error:
Source "xyz" returned not supported result: "undefined"If I return just undefined (i.e. not wrapped in { value }), serverless gives error:
Unexpected "xyz" source result: undefinedIf I return { value: null }, serverless gives error:
Value not found at "xyz" sourceFor context, I want to use this to pass an optional parameter:
MyLayer:
Type: AWS::Lambda::LayerVersion
Properties:
Content:
S3Bucket: ${myresolver:bucket, ''}
S3Key: ${myresolver:key, ''}
S3ObjectVersion: ${myresolver:objectVersion}
Hi all, does anyone know if it's possible to have conditional resources defined, based on the stage?
The use case is that prod and staging stages use a VPC, but dev does not. I am creating a Security Group under resources, which is what I want to make conditional based on the stage.
Does anyone know what has replaced this method?
When is the
stage parameter resolved in serverless? I see that it can be passed to both the package and deploy command, but it seems to be injected during packaging. Is it possible to have this resolved at deploy-time, to enable build-once + promote artifact deployments?
1 reply
curious if anyone has opinions or examples on using ORM to set up dynamo from a serverless typescript project?
1 reply
different question, I want to define iam permissions specifically for a lambda but I'm getting an error that "iam" is an unrecognized property in 'functions.hello' (I'm basing this off the nodejs typescript template)
2 replies
Is that different from the IAM role that lambda itself runs with (seems like it should be)?
Hi
Does anyone met following. error while deploying serverless
Does anyone met following. error while deploying serverless
node:899) ExperimentalWarning: The fs.promises API is experimental
Type Error [ E R R_ I N V A L I D_ A R G_ T Y P E] ------
TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type Function. Received type undefined
at promisify (internal/util.js:256:11)
at Object.<anonymous> (/usr/lib/node_modules/serverless/node_modules/compress-brotli/src/index.js:9:18)
@swetankkk: I was just running into that error, in my case I needed to install each of the plugins referenced in my plugins section of serverless.ts, so 'serverless plugin install -n serverless-offline' 'serverless plugin install -n serverless-dynamodb-local', and then set it up with 'serverless dynamodb install' because my project is using a dynamodb
I think the enoent is a pretty generic error that gets thrown. the fact it can't find that specific file makes me think a config to copy that file to output is missing or something. full discretion I've only been looking at serverless for a bit over a week though
for my own question: I see the serverless debug reference says to use node-inspector which I think is deprecated. I've been struggling to get debugging working from vs code to my offline lambdas. I started referencing this stackoverflow but haven't gotten it totally working either. I'm able to debug from chrome at the serverless entry point, but I can't figure out how to get a breakpoint in my lambda code
I've got a serverless project working offline with dynamo, but when I deploy to aws the lambda exits before the write happens. I've added log statements everywhere so I can see it is precisely at the write call that it fails. not sure how to debug this any further
4 replies
is there a good way to reference the variable ${sls:stage} within actual code of a function? would I need to set it as a environment variable and reference it that way?
1 reply
@jamesmoey: thanks for the feedback! first comment, I had both some async stuff wrong and some permissions, I got it sorted out though! I need to sort out some exception handling in my source.
I also figured out that I can reference environment variables and get the code completion I was looking for, it is working great!
I also figured out that I can reference environment variables and get the code completion I was looking for, it is working great!
now I'm trying to figure out how to export an arn on cfn build
or actually, I'm trying to figure out how to export the api gateway endpoint url so I can do a find replace on the url it generates, it's basically a url shortener I'm building
it changes every time I do a clean deploy
yeah I think you're right. the api is printed on console when I deploy, I just need to persist it to an evironment variable
specifically the authorizer key for serverless version 3. It doesn't recognise identitySource or resultTtlInSeconds like the http event