This is a Bug Report

Description

• What went wrong?

  • When ${ssm} specifiyes non-existant parameter, sls deploy or other command just output warning and continue, instead of throwing error.

• What did you expect should have happened?

  • If parameter is not found and no fallback found, serverless should abort to prevent broken deployment.
  • Note: ${cf} and ${s3} can abort if not found.

• What was the config you used?

service: aws-nodejs

provider:
  name: aws
  runtime: nodejs8.10

functions:
  hello:
    handler: handler.hello

custom:
  ssmVar: ${ssm:/path/to/service/myParam}

• What stacktrace or error message from your provider did you see?

$ sls print
 
 Serverless Warning --------------------------------------
 
  A valid SSM parameter to satisfy the declaration 'ssm:/path/to/service/myParam' could not be found.
 
 
 Serverless Warning --------------------------------------
 
  A valid SSM parameter to satisfy the declaration 'ssm:/path/to/service/myParam' could not be found.
 
service: aws-nodejs
provider:
  name: aws
  runtime: nodejs8.10
functions:
  hello:
    handler: handler.hello
custom:
  envVar: fallback
  optVar: fallback
  selfVar: fallback
  fileVar: fallback

Similar or dependent issues:

• Serverless should throw error when resolution of a variable crashes #3367: Serverless Variables should throw error when the referenced file is not found
• Feature Request: CLI command to check that all SSM params are present #4447: Feature Request: CLI command to check that all SSM params are present
• Option to fail fast on unresolved variables #5369: feature: option to fail fast on unresolved variables
• Undefined variables being casted to the "undefined" string #3491 (comment): Serverless would end up with an error in case it finds any variable that does not exist