Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 16 2019 18:39

    carlosandrebp on master

    upload email icon (compare)

  • Jan 15 2019 14:03

    carlosandrebp on master

    Icons update (compare)

  • Nov 13 2018 16:54
    hassankhan commented #3
  • Nov 02 2018 15:10
    hassankhan commented #3
  • Nov 02 2018 15:10
    hassankhan commented #3
  • Nov 01 2018 23:19
    hassankhan commented #3
  • Oct 29 2018 16:32
    hassankhan commented #3
  • Oct 24 2018 14:38
    hassankhan opened #3
  • Aug 14 2018 23:50

    carlosandrebp on master

    updates animations (compare)

  • Jul 19 2018 16:34
    brianneisler closed #1
  • Jul 19 2018 16:34
    brianneisler commented #1
  • Jul 18 2018 16:36

    andrepiresbp on master

    Updates (compare)

  • Jul 18 2018 15:50

    andrepiresbp on master

    Update (compare)

  • Jul 09 2018 19:25
    gornostal commented #59
  • Jul 09 2018 19:12
    maheshmasale commented #59
  • May 24 2018 23:39
    DavidWells removed as member
  • Feb 13 2018 19:40
    ivan-myob commented #54
  • Feb 08 2018 08:48
    julien2x opened #62
  • Dec 22 2017 16:14
    awcheng opened #61
  • Oct 23 2017 19:12
    dluu2015 closed #60
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)`

or

`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
Denis Pshenov
@ifeltsweet
Hi guys, is there a way to limit the execution of a schedule event that runs every minute to a maximum of one concurrency? So that if the previous cron run didn't finish next one won't start. Does reservedConcurrency achieve that?
Gareth McCumskey
@garethmcc
@ifeltsweet Yes it does. However, its very easy just to try it out to see if it does what you need it to do
Denis Pshenov
@ifeltsweet
@garethmcc Thanks for the confirmation. I tried it using serverless offline and it didn't work, so I wanted a confirmation from someone who's done it before in production. I guess I should raise it with them.
Omar Dulaimi
@omar-dulaimi

Hello,

I'm deploying multiple stages and have noticed that each deployment is created with a different api gateway id resulting in a different url for each stage.

We would like to have all of our stages on the same url:

https://123.execute-api.us-east-1.amazonaws.com/production/graphql
https://123.execute-api.us-east-1.amazonaws.com/staging/graphql
Is that possible?

I couldn't find any docs about that.

Himanshu Joshi
@himharsh1997
No, you need to have a different URL for all environments for better isolation and less confusion.
Omar Dulaimi
@omar-dulaimi
if so, then what's the point of /stage in the url?
since from aws console you would see a single stage for each project
note that I'm deploying these stages from different branches
master => production
staging => staging
Also, We're not considering using a custom domain like api.domain.com, since we're planning to use cloudfront origins later on
Himanshu Joshi
@himharsh1997
So, how single url able to decide which DB, and backend it should hit if we have single URL. We can have single URL of one stage deployed in different region using route53 but not for this case.
yes but how your testers get to know if they testing in staging/qa
Omar Dulaimi
@omar-dulaimi
I get your point, but I dont see why we have to have a different deployment for each stage. it would make it a lot simpler to just hardcode the same base url, and then just change the stage value according to one's needs
I mean api gw already support that
So why not expose it to us
Himanshu Joshi
@himharsh1997
or just set keys in aws ssm and create pipeline file which do that for you. Like /project/<sstage>/<variable>
just button work
you can put other checked in pipeline so no manual work.
Omar Dulaimi
@omar-dulaimi
I honestly don't get what you mean by that. Is it documented somewhere so I could read more about it?
Himanshu Joshi
@himharsh1997

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

Error: EIO: i/o error, chmod '/folder/demo-api/.webpack/getFunction1/node_modules/aws-appsync/node_modules/graphql/module/type/definition.js'

 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.2
SDK Version: n/a
Components Version: 3.7.7

I trying to deploy our project in aws-appsync and our bitbucket pipeline breaking due to this.
Can anyone help use. It's urgent.
It's coming from serverless.
Simi
@kaurthing_twitter
#
tenant-mgmt-service: # 84134: 25 of 26 promises have settled
tenant-mgmt-service: # 84134: 1 are taking longer than expected:
tenant-mgmt-service: # 84134: cf:vlncc-resources-lambda-sandbox.TokenAuthorizerLambdaArn waited on by: ${cf:vlncc-resources-lambda-sandbox.TokenAuthorizerLambdaArn} ${cf:vlncc-resources-lambda-sandbox.TokenAuthorizerLambdaArn}
tenant-mgmt-service: # This can result from latent connections but may represent a cyclic variable dependency
tenant-mgmt-service:
how can this be dealt with?