The --stage parameter ignored when looking for the right .env file

[AndreyTomilinXmpi]

I'm running the serverless script with the next command line:
client deploy --stage prod --region eu-west-1 --aws-profile MyProfile

As you see I'm specifying the --stage parameter, which according to this documentation should use the .env.prod file.

But I'm getting this message:
Serverless: DOTENV: Could not find .env file.

All .env files are in sub-folder envs and here is my serverless config:

service: my-sevice-${opt:stage, self:provider.stage}

frameworkVersion: ">=1.1.0 <2.0.0"

plugins:
  - serverless-finch
  - serverless-dotenv-plugin

custom:
  dotenv:
    basePath: ./envs/
    include:
      - MY_VARIABLE

  ...

provider:
  name: aws
  runtime: nodejs12.x
  stage: ${opt:stage, 'develop'}

[edu-aguilar]

Im having the same problem.

[colynb]

Thanks, I will look at this

[colynb]

The env resolution checks for env in the following order. Can you check to see if these are not set to make sure they are not taking precedence?

process.env.NODE_ENV || options.env || options.stage || 'development'

[colynb]

https://www.loom.com/share/255cf1fdd74a4a2e93d11106841557b8

[AndreyTomilinXmpi]

Hi Colynb!
Big thanks for your fast reply, Even with video.
I tried to create small standalone sample, but was unable to reproduce this problem. Everything worked as expected.
I will try to reproduce this issue on original project later, may be even next week. Don't have time for that right now.

Maybe @edu-aguilar will provide his example.

Thanks again!

[AndreyTomilinXmpi]

Finally I had time to recheck this issue. I have two different folders with serverless.yml. The above issue happens only in one of them. It looks like the problem relates to versions of some depended package(s). I was unable to determine which one (it's not the serverless-dotenv-plugin itself).
The only thing I can say for sure that if you perform clear installation - everything works as expected. I got my folders from other people, so not sure what other packages and in what order (may be it's important?) they installed.

For now think you can close this issue.

Thanks for help!