dashboard-plugin icon indicating copy to clipboard operation
dashboard-plugin copied to clipboard

Serverless deployments are missing configurations in AWS deployments

Open j-collier opened this issue 4 years ago • 1 comments

Bug Report

Description

Deployed AWS lambdas in the newest version of Serverless are logging the following error

2020-02-01T20:11:19.016Z 925ef102-35b3-4965-8204-afb519f623cc ERROR Invoke Error
{
  "errorType": "Error",
  "errorMessage": "ServerlessSDK: Missing Configuration - To use MALT features, \"orgUid\" is required in your configuration",
  "stack": [
    "Error: ServerlessSDK: Missing Configuration - To use MALT features, \"orgUid\" is required in your configuration",
    " at new e.exports (/var/task/serverless_sdk/index.js:9:162588)",
    " at c.transaction (/var/task/serverless_sdk/index.js:9:84571)",
    " at Runtime.handler (/var/task/serverless_sdk/index.js:9:85640)",
    " at Runtime.handleOnce (/var/runtime/Runtime.js:66:25)"
  ]
}
  1. What did you do?

I upgraded to Serverless version 1.62.0 and attempted to deploy my application. All of my lambda endpoints returned an error after deploying. I downgraded to 1.61.3 and did not experience this issue.

  1. What happened?

I got the error above. It's also unclear to me what orgUid is or where to find it or where to set it.

  1. What should've happened?

My application should have deployed as normal and not returned ServerlessSDK errors.

  1. What's the content of your serverless.yml file?

Here's a link to my serverless.yml file that is unchanged during this upgrade: https://gist.github.com/j-collier/f823e4db24e1698cbed87b492f65ed55.

  1. What's the output you get when you use the SLS_DEBUG=* environment variable (e.g. SLS_DEBUG=* serverless deploy)

The deployment is successful, the error only happens after deployment. The errors are not logged in the serverless dashboard, for some reason

j-collier avatar Feb 03 '20 05:02 j-collier

@j-collier thanks for report.

We need a bit more info to track that. Can you paste the output of sls --version for both cases (when you use 1.61.3 an deployed functions run ok, and when you use 1.62.0 and deployed functions fail).

Additionally can you provide us with sls deploy command output, with SDK_HTTP_DEBUG=* and SLS_DEBUG=* turned on?

Also it'll be great to have it for deployments with both versions.

medikoo avatar Feb 10 '20 20:02 medikoo