1.2.0 breaks serverless interpolation

Hi there,

I love your plugin and I use it for my current pet project. I guess something has broken in the last version. This works in 1.1.5

custom:
  dotenv:
    path: .${self:provider.stage}.env

It will load stage specific files like .dev.env. In 1.2.0 it can’t find the file anymore. envPath is just .${self:provider.stage}.env. I think this related to change when the plugin loads the env file.

Thanks!

[colynb]

Yeah it turns out that I accidentally introduced a breaking change. There’s an issue where I couldn’t do variable interpolation on the provider section like when you want to use an env var for setting the region. The fix for that introduced a chicken and egg problem that I need to fix.

On Tue, Aug 7, 2018 at 2:54 PM Benjamin Otto [e-mail] wrote:

Hi there,

I love your plugin and I use it for my current pet project. I guess something has broken in the last version. This works in 1.1.5

custom: dotenv: path: .${self:provider.stage}.env

It will load stage specific files like .dev.env. In 1.2.0 it can’t find the file anymore. envPath https://github.com/infrontlabs/serverless-dotenv-plugin/blob/master/index.js#L21 is just .${self:provider.stage}.env. I think this related to change when the plugin loads the env file.

Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/infrontlabs/serverless-dotenv-plugin/issues/19, or mute the thread https://github.com/notifications/unsubscribe-auth/ABACJHQPNO7Vm9hQIqaQkoNUwwHelqSuks5uOgyugaJpZM4Vy84r .

[otbe]

Dont know 😕 At a first glance I thought --env is an alias to set NODE_ENV and I skipped the rest of the docs. But its mentioned quite well that --env should be used if you cant set NODE_ENV. So this should be fine 🤔