[Enhancement]: Push users toward better practices

[JerryNixon]

What happened?

Can we update dab init to create a .env file when a connection string is supplied?

Details:

1. Create the .env file
2. Use a default environment variable name my-connection-string

Simple .env file contents:

my-connection-string=whatever-the-user-provided

3. Reference the environment variable name in the dab-config.json file.

Using variables in the JSON:

{
  "$schema": "...",
  "data-source": {
    "database-type": "mssql",
    "connection-string": "@env('my-connection-string')"
  }
}

Possible additional:

4. Auto-create a .gitignore ignoring the .env file.

Simple .gitignore file contents:

.env

Considerations:

1. What to do when there is already a .env file?
2. What to do when there is already a .gitignore file?

Version

Future

What database are you using?

Azure SQL

What hosting model are you using?

Local (including CLI)

Which API approach are you accessing DAB through?

REST, GraphQL

Relevant log output

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct