This PR adds generation of .env file after the boilerplate code is generated (both JS and Python). The .env contains provider integration params and security scheme variables that are expected in the application code.
It respects potential previous .env file in that it only adds variables that are missing in the previous `.env.
You can go through commit by commit.
Tasks:
[x] Create dotenv utility that takes optional previous .env with provider definition and creates a new .env
[x] Integrate dotenv utility to boilerplate codegen process (interact with filesystem)
Motivation and Context
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[ ] I have updated the documentation accordingly. For updating Oclif commands documentation use oclif-dev.
Description
This PR adds generation of
.envfile after the boilerplate code is generated (both JS and Python). The.envcontains provider integration params and security scheme variables that are expected in the application code.It respects potential previous
.envfile in that it only adds variables that are missing in the previous `.env.You can go through commit by commit.
Tasks:
.envwith provider definition and creates a new.envMotivation and Context
Types of changes
Checklist: