yml file inclusion about aws-utils HOT 6 OPEN

@cbaron Let's re-evaluate passing env to lambda. Seems like it's useful.

from aws-utils.

Good question! It should given we use serverless directly to parse the config but if it's not working for you then clearly we need to fix something. Does using an absolute path work? What is the error?

from aws-utils.

I use file inclusion to include environment variables and then use in from my lambdas. In lambda they available under process.env but when I use it with emulator all they are undefined so I suppose that file inclusion format may be not supported by emulator or I'm missing something...

Does using an absolute path work?

the same in this case:

environment: ${file(env.yml):${self:provider.stage}}`

and in case with absolutely absolute path. The only content of process.env is

{ DYNAMODB_ENDPOINT: 'http://localhost:62224/' }

from aws-utils.

as far as I see now, the problem is not in yml file inclusion, but it is in not passing values from provider.environment to lambda's process.env.

from aws-utils.

any updates on this? do you plan to implement this?

from aws-utils.

I will try to carve out some time this week. As always, you're welcome to put up a PR.

from aws-utils.