How to set different/separated env vars per function?

[delgermurun]

Hello,
Thank you for creating an amazing useful library.

Can I set some vars only for one(or more) functions in a project?

Thanks.

[redlickigrzegorz]

It's a very good question. I didn't find any possibility to set this with the usage of this library that's why I decided to create my own config.js file to keep all the needed env variables and put them where I want during the work with serverless 😃

@colynb is it possible to do this via your library?

[colynb]

Would you mind describing a use-case/scenario so that I can get a better understanding? Thanks

[redlickigrzegorz]

@colynb Yes, of course, and I believe that it will be a simple example 😉

functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

[ChristopheBougere]

I'm having a similar use case: I want to load env variables in my fargate task definition, but not in my lambda functions.
Your snippet should work if you add this setting:

custom:
  dotenv:
    include: [] # Do not inject env variables into lambdas

Having an option to disable auto injection could be great by the way :)

[tommykamkcm]

@colynb Yes, of course, and I believe that it will be a simple example 😉

functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

Hello everyone, I have additional questions about this scenario:

Assuming there are 10 env vars declared in .env e.g. SAMPLE_A ... SAMPLE_J
What happens to sample-funtion-a if we declare:

• SAMPLE_C ... SAMPLE_J under custom > dotenv > include, and also

• SAMPLE_A under sample-function-a

will sample-function-a get all the env vars except SAMPLE_B?

[krlozadan]

Hi, any updates on this?

@colynb Yes, of course, and I believe that it will be a simple example 😉

functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

This will definitely be very helpful

[colynb]

@krlozadan sorry for the VERY late response. I've been using today to get caught up on this plugin. As I mentioned in a few other issues here recently, I'm extremely nervous about accidentally introducing breaking changes so I erred on the side of simply ignoring these requests.

With that said, this is definitely one of the trickier requests to implement. I'm not sure how I would even approach it.

[neverendingqs]

@colynb Yes, of course, and I believe that it will be a simple example wink

functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

Hello everyone, I have additional questions about this scenario:

Assuming there are 10 env vars declared in .env e.g. SAMPLE_A ... SAMPLE_J
What happens to sample-funtion-a if we declare:

• SAMPLE_C ... SAMPLE_J under custom > dotenv > include, and also
• SAMPLE_A under sample-function-a

will sample-function-a get all the env vars except SAMPLE_B?

I am 90+% sure of the following. Please test my statements below if you would like to be 100% sure.

Environment variables defined with dotenv end up at the project level according to

serverless-dotenv-plugin/index.js

Lines 120 to 122 in 2b66c15

	Object.keys(envVars).forEach((key) => {
	this.log('\t - ' + key)
	this.serverless.service.provider.environment[key] = envVars[key]

.

In your example, sample-function-a will include SAMPLE_B ... SAMPLE_J from the dotenv file(s) because it pulls it from the project level.

Furthermore, environment variables with the same name defined at the function name takes precedence over ones defined at a project level. This means sample-function-a's SAMPLE_A value is whatever you declare it to be. In your example, because you set it to ${env:SAMPLE_A}, sample-function-a's SAMPLE_A value will be the same as the one in the dotenv file(s).

[neverendingqs]

I'm having a similar use case: I want to load env variables in my fargate task definition, but not in my lambda functions.
Your snippet should work if you add this setting:

custom:
  dotenv:
    include: [] # Do not inject env variables into lambdas

Having an option to disable auto injection could be great by the way :)

This is my recommendation as well. Please see #89 for details.

[neverendingqs]

I think all questions have been answered. Because there are a variety of questions here, if you have a follow-up question or a related question, please post it in https://github.com/neverendingqs/serverless-dotenv-plugin/discussions/categories/q-a.

Thanks!