Some, not all, environment vars are missing

[bebbi]

Environment variables are not all available to functions. Only the variables defined globally and those for the first function will be available when running locally. Example:

serverless.yml:

provider:
  environment:
    A: 'A'
functions:
  func1:
    environment:
      F1: '1'
  func2:
    environment:
      F2: '2'

In this setup, the only variables available to the local environment are A and F1.
If I move func2 on top of func1, it is however A and F2.

[bebbi]

I found why this is happening.

webpack has created a single handler.js function containing both functions, which means that at set up time of func1, func2 is also loaded which immediately leads to a failure as func2 needs its environment but doesn't have it available.

[kevinold]

I tested this with my project and unfortunately I'm still missing all environment variables in my handlers :(

[HyperBrain]

@bebbi Version 3.0.0 will integrate with serverless invoke local and the serve command will be removed in favor of the serverless-offline plugin (see Milestone 3.0.0). This should also fix the environment variable issue completely.
My PR #153 already works - only the unit tests are missing. Could you try it with that and tell me, if it works as expected?

[HyperBrain]

serve will be removed in the next v3.0.0 release in favor of serverless-offline (see #152 ). No efforts will be spent on the function anymore. So I'll close this issue.

[bebbi]

I’ll move to offline, I appreciate your efforts very much.

…

On 28 Jul 2017, at 20:02, Frank Schmid ***@***.***> wrote: serve will be removed in the next v3.0.0 release in favor of serverless-offline (see #152 <#152> ). No efforts will be spent on the function anymore. So I'll close this issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#99 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACn_h53ZCZ4u_Zyhq9gnw6tyQv7RueAUks5sSiJDgaJpZM4MAvOH>.