Lukas Siemon

We just ran into this as well (moving from the deprecated `request` library to `axios`). So would very much appreciate if this old ticket could be picked up again! Cheers

For anyone looking, I'm working on this functionality for [node-tdd](https://github.com/blackflux/node-tdd) in this [pull request](https://github.com/blackflux/node-tdd/pull/760/files). @gr2m Pr is fully functional, but could probably be improved. Would love if you could take...

Is there a way to achieve this by using different contexts? E.g. you could use function + service environment variables. Is there a more generic way?

@horike37 Would you mind pointing me to the relevant file(s)? I'd like to make this my first contribution! Cheers

@horike37 Thank you for the input! @HyperBrain As far as I can see currently `load` is used. Where are you seeing `safeLoad`?

Seems like https://github.com/whitlockjc/json-refs is used to resolve the dependencies after the yaml is parsed. It makes sense that we are seeing this error. Any objections to restructuring it so that...

@erikerikson Ah yes. Sorry I wasn't clear at all. There are three stages; (1) yaml parsing (2) json-ref processing and (3) variable resolution Basically the syntax we want to support...

The plugin [serverless-merge-config](https://github.com/CruGlobal/serverless-merge-config) should resolve this. Big thanks to @Omicron7 - However there seem to be other problems with parameter resolutions. Considering how important config resolution is and how many...

@simonbuchan @thomasmichaelwallace Might be interesting for reference: https://github.com/serverless/serverless/issues/4817#issuecomment-372499260 Edit: Here is the important file https://github.com/simlu/lambda-serverless-api/blob/master/lib/util/yaml.js

Based on discussion with @erikerikson I'm detailing our use case a bit more. We have two separate stacks that we deploy with serverless: One `data` stack that we deploy when...