Add support for .env file

[abhishekkumams]

Why make this change?

• Closes Add support for providing environment var/values in a .env file read by dotenv.net #1374
  • To allow users maintain a local .env to manage environment variables during local development.

What is this change?

• Using the package DotNetEnv
• Now, users can maintain a local file .env to manage environment variables instead of setting environment variables in the system.
• If .env file is used, it will take precedence over system environment variables.

How was this tested?

• Unit Tests

NOTE:

• This feature is to enhance local development experience, and it works when used via DAB CLI.

QnA

1. Where should the .env file be created?
   -> For .env file to be considered, it should be present in the same directory where the dab commands are executed.

2. Does it overwrite the existing environment variables?
   -> No, it doesn't update any existing variables. It just gives precedence to the variable defined in the file over the system defined variable in case it is present in both places.

[seantleonard]

PR description:

If .env file is not used, it will take precedence over system environment variables.

should the line read: "If .env file is used" ?

[seantleonard]

Some questions

updated

[seantleonard]

some additional suggestions.

[ayush3797]

Some nits. LGTM otherwise!

[Aniruddh25]

Not sure why we are testing DotNetEnv.Env.Load externally.

[abhishekkumams]

Not sure why we are testing DotNetEnv.Env.Load externally.

We have tests that verifies DotNetEnv.Env.Load internally. Line:125(Environment)

we have some external tests as well to just verify the method ParseConfigJsonAndReplaceEnvVariables as calling this directly won't load the variables from .env file.

Loading from .env file happens at the initialization step of DAB CLI, so that every cli command is synced with the environment variables.

Hope this addresses your concerns?

[Aniruddh25]

Not sure why we are testing DotNetEnv.Env.Load externally.

We have tests that verifies DotNetEnv.Env.Load internally. Line:125(Environment)

we have some external tests as well to just verify the method ParseConfigJsonAndReplaceEnvVariables as calling this directly won't load the variables from .env file.

Loading from .env file happens at the initialization step of DAB CLI, so that every cli command is synced with the environment variables.

Hope this addresses your concerns?

Thanks for the clarifications, could you comment the additional scenarios which this test is handling.

[abhishekkumams]

Not sure why we are testing DotNetEnv.Env.Load externally.

We have tests that verifies DotNetEnv.Env.Load internally. Line:125(Environment)
we have some external tests as well to just verify the method ParseConfigJsonAndReplaceEnvVariables as calling this directly won't load the variables from .env file.
Loading from .env file happens at the initialization step of DAB CLI, so that every cli command is synced with the environment variables.
Hope this addresses your concerns?

Thanks for the clarifications, could you comment the additional scenarios which this test is handling.

Sure, For Example we are:

• testing that there are no breaks using the original method for using environment variable.
• testing scenarios where we have variables defined in both system and .env file

updated