Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deploying does not rely on artifact config parameter

See original GitHub issue

This is a bug report

What went wrong?

Running sls deploy does not take the artifact parameter into account, it zips the whole directory and deploys it rather than just take the artifact.

What did you expect should have happened?

sls deploy should (it did yesterday):

Deploy artifact zip file when it exists;
Fail when artifact zip file does not exist

What was the config you used?

service: poipoi

frameworkVersion: ">=1.12.0"

provider:
  name: aws
  runtime: python3.6
  stage: dev
  region: us-east-1
  memorySize: 128
  timeout: 300
  # KMS Key used for encryption/decryption
  kmsKeyArn: arn:aws:kms:us-east-1:XXXXXXXXX:key/XXXXXXX

package:
  artifact: poipoi.zip

custom:
  actual_stage: ${opt:stage, self:provider.stage}
  dev:
    audience: XXXXXXX
    client_id: XXXXXXX
    # client_secret is encrypted using KMS poipoi/lambdas
    # $ aws kms encrypt --key-id alias/poipoi/lambdas --plaintext <secret>
    client_secret: |
      AXXXXXXXXXXXXXXXXXXXXXXdqT/KPS365PqQ4jY5Vi64RpFiVwAAAKIwgZ8GCSqGSIb3DQEHB
      XXXXXXX...
    log_level: DEBUG
    oauth_token_url: XXXXXXX
    poipoi_url: XXXXXXX


functions:
  poipoi:
    handler: poipoi.handler
    events:
      - stream: arn:aws:kinesis:us-east-1:XXXX:stream/XXXXX-${self:custom.actual_stage}
    environment:
      poipoi_url: ${self:custom.${self:custom.actual_stage}.poipoi_url}
      client_id: ${self:custom.${self:custom.actual_stage}.client_id}
      client_secret: ${self:custom.${self:custom.actual_stage}.client_secret}
      audience: ${self:custom.${self:custom.actual_stage}.audience}