serverless/serverless

For support requests please search or create posts on Serverless Forum: https://forum.serverless.com

Ellery Familia

@ElleryFamilia_twitter

We have 2-factor authentication set up in the AWS account. sls deploy command thus asks for the MFA code. How to run the deployment in non-interactive mode when MFA is enabled?
For ex:
lerna run
command does not support user input. Similarly, if this was to run in CI/CD, interactivity won’t be possible. How is this handled. What’s the best way to manage this in serverless framework with sls deploy command?

Did you add AWS as a provider on serverless? I also have 2-factor on but have never been asked to provide an MFA code when deploying

drixone-coder

@drixone-coder

has anyone ever taken a canary deployment project with serverless before??

i have been assigned a task to do so.Dont know if any of you have ideas?

Gareth McCumskey

@garethmcc

@drixone-coder Perhaps this will help? https://www.serverless.com/blog/manage-canary-deployments-lambda-functions-serverless-framework

Steve Willard

@stevewillard

👋 Hi everyone! We’re excited to announce that ⚡️ Serverless Desktop ⚡️ is in beta. Check it out here: https://github.com/serverless/desktop

Serverless Desktop is a GUI client designed to streamline your Serverless dev workflow. A few highlights:

Invoke functions via HTTP or directly
Stream logs in real time
Watch for function changes, and auto re-deploy
Save queries, and share them with teammates
A simple DynamoDB table viewer and editor
A simple S3 bucket viewer

We would love your feedback to help us build something you love. Please take 2 minutes to answer these 4 questions.

Andreas Kohn

@ankon

:confused: the repo says MIT licensed, but there's only a macOS(?) binary and no sources?

Steve Willard

@stevewillard

@ankon Hi there. The license was added by mistake - thanks for pointing that out. Desktop, for now, is closed source. We have plans to release Windows and Linux binaries in the near future.

Ellery Familia

@ElleryFamilia_twitter

@stevewillard No way to login with my serverless user/pass

Steve Willard

@stevewillard

@ElleryFamilia_twitter Username/password (non-social auth) is coming soon. But, you can actually login via the CLI. Desktop and the CLI share the same session.

Ellery Familia

@ElleryFamilia_twitter

got it… I was already logged in to CLI, so just had to run the sls login command again and it worked

asking for me to connect my AWS account, although it’s already connected

Steve Willard

@stevewillard

At the moment, Desktop asks you to create a new, dedicated IAM Role for your account(s). Out of curiosity, do you already have a Serverless Provider configured?

Ellery Familia

@ElleryFamilia_twitter

Yes, I have a provider configured

Gareth McCumskey

@garethmcc

@ElleryFamilia_twitter This is because we actuially aim to have desktop be seperate from what you usually use to deploy with and the permissions needed would be managed directly by desktop itself so that we will, in future, create IAM permissions with the bare minimum needed, but we don't want to interfere with the permissions your other services needed or depend on those.

Ellery Familia

@ElleryFamilia_twitter

So you’re saying that if I connect the same AWS Provider on desktop as I have on your website, there’s a chance of a collision or potential issues with deployments? Is Desktop only for folks startign anew not planning on using web/cli?

Steve Willard

@stevewillard

The AWS Provider used for deployments is independent of the one used for Desktop, so there is no chance of collision. Desktop is for any Serverless user, which includes non-dashboard (web) users.

Gareth McCumskey

@garethmcc

@ElleryFamilia_twitter And not a collision, just that in future the permissions set in the desktop IAM role may not be sufficient to use for deploying your AWS services as we will be attempting to ensure minimal IAM permissions in future

Alexander Mills

@agjmills1_twitter

hi, I'm new to serverless framework and I have a few noobish questions. Why do I have the dependency of serverless-python-requirements and serverless-wsgi from npm? How are they used under the hood?

1 reply

^ meant to add, when writing serverless endpoints in Python for AWS Lambda

Alexander Mills

@agjmills1_twitter

is there a way of generating application scaffolding from an openapi spec?

clmn

@JacksonGariety

d36f2685bg2d5j.cloudfront.net

clmn

@JacksonGariety

How can I get the CloudFront distribution ID in my serverless template?

rwh2Moen

@rwh2Moen

HI all, I have what I hope is an easy question. For serverless, can I use native CloudFormation. The reason I ask is because Serverless does not appear to support AWS Pinpoint. thanks

rwh2Moen

@rwh2Moen

I just figured it out. Thanks.

Omri Haim

@omrihaim

Hi everyone. I am new to serverless.com. Does anyone knows how can we use AWS lambda example that isn't available as one of serverless existing examples?

6 replies

drixone-coder

@drixone-coder

Serverless: Configuration warning:
Serverless: at 'service': unrecognized property 'package'
Serverless: at 'resources.Resources.SPoGOrderManagementUpdateQueue.DependsOn': should be array
Serverless: at 'resources.Resources.SPoGOrderManagementCreateQueue.DependsOn': should be array
Serverless: at 'resources.Resources.SPoGOrderManagementAckPaymentInfoQueue.DependsOn': should be array

Hi guys so i found this error while trying to sls deploy .i don't know what this could be .Has anyone had any issue like this?

4 replies

Simi

@kaurthing_twitter

How to do a logical not in serverless .yml file?

something like enable: !${self:custom.log.disable}

Gareth McCumskey

@garethmcc

@kaurthing_twitter Could you share the problem you are trying to solve? A logical not is not available but there is usually another way to solve these issues

rwh2Moen

@rwh2Moen

hi All, I am wondering if you might be able to help with a problem of custom _env files not getting their values read?

deploy line
sls deploy --region ca-central-1 --stage dev

serverless.yml
custom: ${{file(serverless/config/custom_${{self:provider.stage}}.yml)}}

custom_dev.yml
APPLE_AUTH_METHOD: get this from Apple/Miguel APPLE_PVT_KEY: get this from Apple/Miguel

service.yml

SnsGoogleAlertPinpointChannel: Type: AWS::Pinpoint::GCMChannel Description: Google (Android) SNS Push Notifications Channel for sending Alerts and Notifications to the user Properties: ApiKey: ${{self:provider.environment.GOOGLE_API_KEY}} ApplicationId: ${{self:provider.environment.PP_APP_NAME}} Enabled: true

1 reply

Michael Connors

@mcmikeyy

Hi All, I have a problem that you might be able to help with.

simple helloworld type nodejs endpoint using serverless-bundle.

This fails when using yarn or npm as the custom.bundle.packager.

`Serverless: Bundling with Webpack...
Serverless: Fetch dependency graph from /home/michael/work/serverless/sls-course/notes-api/package.json

Error --------------------------------------------------

Error: yarn list --depth=1 --json --production failed with code 1
at ChildProcess.<anonymous> (../notes-api/node_modules/serverless-webpack/lib/utils.js:91:16)`

`Serverless: Bundling with Webpack...
Serverless: Fetch dependency graph from ../notes-api/package.json

Syntax Error -------------------------------------------

SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at ../notes-api/node_modules/serverless-webpack/lib/packagers/npm.js:70:49`

Your Environment Information ---------------------------
Operating System: linux
Node Version: 12.19.0
Framework Version: 2.28.6
Plugin Version: 4.4.3
SDK Version: 2.3.2
Components Version: 3.7.2

the addition of the serverless-bundle it fails when not present it deploys ok.

Any Ideas?

3 replies

donkindred

@donkindred

I'm new to Serverless and trying to build a Google DialogFlow api with AWS Lambda in Node.js. Every time I log event in my js, it's an empty string. Any ideas?

module.exports.app2 = async event => {
  return {
    statusCode: 200,
    body: JSON.stringify(
      {
        message: 'Go Serverless v1.0! Your function executed successfully!',
        input: event,
      },
      null,
      2
    ),
  };

Walid Karray

@tux86

Hello,
I'm using serverless version 2.29.0 . I have a monorepo (yarn workspaces) project with multiple microservices. Each microservice has it own serverless.yml config file.
and I have a serverless-common.yml in root of the monorepo referenced by all my microservices I have a lot of redundant variables which i have refactored in this common config file . Today when I run deploy I have a warning like shown below.This will be an error from serverless v3.

Is there any clean workaround to share common variables across all services ?

Cannot resolve serverless.yml: Variables resolution errored with:
    - Cannot resolve variable at "provider.stage": Cannot load file from outside of service folder,
    - Cannot resolve variable at "provider.runtime": Cannot load file from outside of service folder,
    - Cannot resolve variable at "provider.region": Cannot load file from outside of service folder,
    - Cannot resolve variable at "provider.profile": Cannot load file from outside of service folder,
    - Cannot resolve variable at "provider.deploymentBucket.name": Cannot load file from outside of service folder,
    - Cannot resolve variable at "provider.logRetentionInDays": Cannot load file from outside of service folder,
    - Cannot resolve variable at "custom.output.file": Cannot load file from outside of service folder

Simi

@kaurthing_twitter

As running the app from CI-CD pipeline, a profile is not being passed in the argument assuming the pipeline has the required permissions through the role.

My deployment-role.yml file has a policy that looks as follows:

DeploymentPolicy:
Type: AWS::IAM::Policy
Properties:
PolicyName: deployment-policy
PolicyDocument:
Version: 2012-10-17
Statement:

     - Effect: Allow
       Action:
         - 'cloudformation:*'
         - 'iam:*'
         - 'lambda:*'
         - 'ecs:*'
         - 'ecr:*'
         - 'logs:*'
         - 'ssm:*'
         - 'acm:*'
         - 'apigateway:*'
         - 'application-autoscaling:*'
         - 'autoscaling:*'
         - 'cloudfront:*'
         - 'cloudwatch:*'
         - 'elasticache:*'
         - 'elasticloadbalancing:*'
         - 'events:*'
         - 'route53:*'
         - 'sns:*'
         - 'sqs:*'
         - 's3:*'
         - 'dynamodb:*'
         - 'xray:*'
         - 'cognito-idp:*'
       Resource: '*'
 Roles:
   - !Ref DeploymentRole
   -

Given the policy has full access to s3, I expected the deployment to go through but it fails with the following error message:

lerna notice cli v4.0.0

326 | lerna info ci enabled
327 | lerna info Executing command in 4 packages: "npm run deploy"
328 | vlncc-sns: > vlncc-sns@0.1.0 deploy
329 | vlncc-sns: > sls deploy -v
330 | tenant-mgmt-service: > tenant-mgmt-service@0.1.0 deploy
331 | tenant-mgmt-service: > sls deploy -v
332 | vlncc-sns: Serverless: Deprecation warning: Variables resolver reports following resolution errors:
333 | vlncc-sns: - Cannot resolve variable at "provider.profile": Value not found at "opt" source
334 | vlncc-sns: From a next major it we will be communicated with a thrown error.
335 | vlncc-sns: Set "variablesResolutionMode: 20210219" in your service config, to adapt to this behavior now
336 | vlncc-sns: More Info: https://www.serverless.com/framework/docs/deprecations/#NEW_VARIABLES_RESOLVER
337 | tenant-mgmt-service: Serverless: Deprecation warning: Variables resolver reports following resolution errors:
338 | tenant-mgmt-service: - Cannot resolve variable at "provider.profile": Value not found at "opt" source,
339 | tenant-mgmt-service: - Cannot resolve variable at "provider.iamRoleStatements.0": Cannot load file from outside of service folder
340 | tenant-mgmt-service: From a next major it we will be communicated with a thrown error.
341 | tenant-mgmt-service: Set "variablesResolutionMode: 20210219" in your service config, to adapt to this behavior now
342 | tenant-mgmt-service: More Info: https://www.serverless.com/framework/docs/deprecations/#NEW_VARIABLES_RESOLVER
343 | vlncc-sns:
344 | vlncc-sns: Serverless Warning --------------------------------------
345 | vlncc-sns:
346 | vlncc-sns: A valid option to satisfy the declaration 'opt:profile' could not be found.
347 | vlncc-sns:
348 | vlncc-sns: Serverless: Packaging service...
349 | vlncc-sns: Serverless: Creating Stack...
350 | tenant-mgmt-service:
351 | tenant-mgmt-service: Serverless Warning --------------------------------------
352 | tenant-mgmt-service:
353 | tenant-mgmt-service: A valid option to satisfy the declaration 'opt:profile' could not be found.
354 | tenant-mgmt-service:
355 | vlncc-sns: Serverless: Checking Stack create progress...
356 | tenant-mgmt-service: Serverless: Configuration warning at 'functions.getPool.events[0].http': unrecognized property 'documentation'
357 | tenant-mgmt-service: Serverless:
358 | tenant-mgmt-service: Serverless: Learn more about configuration validation here: http://slss.io/configuration-validation
359 | tenant-mgmt-service: Serverless:
360 | tenant-mgmt-service: Serverless: Deprecation warning: Starting with version 3.0.0, following property will be replaced:
361 | tenant-mgmt-service: "provider.iamRoleStatements" -> "provider.iam.

why does it fail? How can I fix this?

Rajat Subhra Ghosh

@rajat85

Hello

I have deployed a lambda function that is exposed via https end point. Now I want to invoke that endpoint when there is a something available in cloud watch log. Can someone please guide me through the steps?

Nima Poulad

@NimaPoulad_twitter

`Serverless: Uploading file at '/Users/.../serverless/azure-example/.serverless/azure-example-ds.zip' to container 'deployment-artifacts' with name 'samplewus2devazureexampleds-ARTIFACT-xxx.zip'

Fetch Error ---------------------------------------------

FetchError: request to https://xxxx.blob.core.windows.net/deployment-artifacts/samplewus2devazureexampleds-ARTIFACT-t1616273156752.zip?blockid=xxxxx&comp=block failed, reason: write EPIPE

Looks like serverless can't upload the zipped files to the blob storage. Any idea why?

Zeeshan Haider

@zeeshanalisyed

Hello guys

I am having a version problem

of runtime on aws

when I execute sls deploy it deploys with the older nodejs version in aws lambda

while my serverless.yaml is given below

org: zeeshanemallates
app: my-lambda-app
name: aws-lambda-starter
component: aws-lambda
provider:
  name: aws
  runtime: nodejs14.x
  stage: dev
  region: us-east-2
inputs:
  src: ./src
  handler: handler.handler

its is not even respecting aws region

I am new to this framework may be I am missing something?

Nima Poulad

@NimaPoulad_twitter

does anyone know how i can reference ARM template outputs in my serverless.yml file? (azure provider)

Zeeshan Haider

@zeeshanalisyed

anyone?

Himanshu Joshi

@himharsh1997

Type Error ---------------------------------------------

TypeError: Cannot read property 'pipesCount' of undefined
at ReadStream.Readable.pipe (_stream_readable.js:637:13)
at Readable.<anonymous> (/opt/atlassian/pipelines/agent/build/node_modules/lazystream/lib/lazystream.js:33:12)
at Readable.instance.<computed> (/opt/atlassian/pipelines/agent/build/node_modules/lazystream/lib/lazystream.js:18:14)
at Readable.read (/opt/atlassian/pipelines/agent/build/node_modules/readable-stream/lib/_streamreadable.js:443:10)
at resume (/opt/atlassian/pipelines/agent/build/node_modules/readable-stream/lib/_stream_readable.js:790:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)

 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com

Your Environment Information ---------------------------
Operating System: linux
Node Version: 12.20.1
Framework Version: 2.17.0 (local)
Plugin Version: 4.5.1
SDK Version: n/a
Components Version: 3.7.5

Getting this error on nodejs project deployment with nodejs@12.20.1

Where communities thrive

People

Repo info

Activity

lerna notice cli v4.0.0