chris-feist / serverless-plugin-composed-vars Goto Github PK

There were apparently breaking changes in the way Serverless loads environment variables recently and this plugin no longer properly resolves the values expected for the stage.

See a similar thread here from serverless-dotenv plugin:
https://www.npmjs.com/package/serverless-dotenv-plugin
serverless>=3.0.0 introduces changes that significantly impacts this plugin. See the discussion thread or the FAQ below for details on the impact of how env vars are loaded with serverless>=2.26.0 and serverless>=3.0.0.

Pipeline went down recently because there was a critical update to mixin-deep dependency (now on 2.0.1, due to a prototype pollution bug).

I can make a quick PR, or if you'd prefer to update it yourself, that'd be great! All that needs to be done is update mixin-deep to 2.0.1.

When using npm instead of yarn, the module fails to install. I like the enforcement of yarn, but also like the library and in my current project cannot switch.

So for a migration of aws accounts it would be really handy to be able to use opt variables in the file name, but they don't get substituted at the moment.
when i pass in
${file(./params/${opt:account}/params.yml)}

with account x
it does not seem to read file ./params/x/params.yml
and ./params/x/params.dev.yml
Could this functionality be added

Add a warning when we encounter a variable defined in the stage specific file, that isn't defined in the default variables