The --stage cli option is not passed to stage property if omitted from serverless.yml file

[tonyallain]

When stage is missing from serverless.yml it will not automatically resolve to a passed in --stage argument, but instead remain as dev. This is dissimilar to the behavior of region which (if omitted from the yml file) will resolve to the passed in --region argument.

This issue was discovered when configuring a plugin to set defaults if none are provided such as VPC configuration and the boilerplate stage and region options/fallbacks.

serverless.yml

service: stage-bug

plugins:
  - ./plugin

provider:
  name: aws
  runtime: nodejs12.x

plugin.js

'use strict';

class ServerlessPlugin {
  constructor(serverless, options) {
    this.serverless = serverless;
    this.options = options;

    this.commands = {};

    this.hooks = {};

    console.log(this.serverless.service.provider);
  }
}

module.exports = ServerlessPlugin;

sls --version --stage production --region potato output

{ stage: 'dev',
  variableSyntax: '\\${([^{}]+?)}',
  name: 'aws',
  runtime: 'nodejs12.x',
  region: 'potato',
  versionFunctions: true,
  remoteFunctionData: null }

Installed version

Framework Core: 1.76.1
Plugin: 3.6.17
SDK: 2.3.1
Components: 2.33.0

[medikoo]

@tonyallain it's actually expected, as service.provider.stage is configured to expose stage as in serverless.yml (eventually defaulting to dev). It's not a source of information for fully resolved stage.

For fully resolved stage use this.serverless.getProvider('aws').getStage().

I agree it's sort of design issue as it's counter-intuitive, but it's it is what it is (at least at this point) :)