Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Property error when multiple functions are defined in serverless.yml #9

Closed
ds0440 opened this issue Jan 15, 2019 · 2 comments · Fixed by #11
Closed

Property error when multiple functions are defined in serverless.yml #9

ds0440 opened this issue Jan 15, 2019 · 2 comments · Fixed by #11

Comments

@ds0440
Copy link

ds0440 commented Jan 15, 2019

When multiple functions are defined within serverless.yml this plugin encounters an unhandled property error during deployment. I think this is because I am not defining a subscriptionFilter event for all of my functions.

$ sls deploy
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Injecting required Python packages to package...

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

  Cannot read property 'logGroupName' of undefined

     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

serverless.yml

service: test-service

provider:
  name: aws
  stage: dev

functions:
  function1:
    handler: function1.lambda_handler
    timeout: 30
    runtime: python3.6
    events:
      - subscriptionFilter:
          stage: dev
          logGroupName: /aws/lambda/logGroup
          filterPattern: ERROR
  function2:
    handler: function2.lambda_handler
    timeout: 30
    runtime: python3.6
    events:
      - http:
          method: POST
          path: /
@tsub
Copy link
Owner

tsub commented Jan 18, 2019

Thank you for reporting this issue.

Surely the problem has been reproduced.
Perhaps it is a degrade in #7.

I will make an effort to solve the problem.

@tsub
Copy link
Owner

tsub commented Jan 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants