This repo contains scripts (powershell & bash) to convert Azure functions local.settings.json files to .env files, or the other way around.

A powershell script (.ps1) and module (.psm1) You can either run the powershell script or use it as a module.

• -FromEnv: Set this to "yes" if you want to convert a .env file to a local.settings.json file. By default, it is set to "no"
• -Path: Set the path to the folder containing the file to convert. By default, it is the current directory

1. In C:\Program Files\WindowsPowerShell\Modules, paste in the folder contained in this repo, with the .psm1 file inside
2. In a powershell window, run Import-Module Convert-SettingsEnv (you don't need to run it several times, just once per session)
3. Run the command Convert-SettingsEnv. You can pass in parameters if you'd like

1. Set the Execution Policy on your machine to RemoteSigned if you've never done it before: Set-ExecutionPolicy RemoteSigned
2. In the folder that contains the script, run . .\convert-settings-env.ps1. You can pass in parameters if you'd like

The convert-settings-env.sh can be invoked directly and supports converting back and forth between .env and local.settings.json.

• -e | --env (optional) flag to convert from env to json. Leave out to convert from json to env. (default json to env)
• -o | --output (optional) Output file. (default is local.settings.json for -e and .env for otherwise.)
• -i | --input (optional) Input file. (default is .env for -e and local.settings.json for otherwise.)
• -f | --force (optional) Skip prompting for existing file. (default: false)
• -v | --verbose (optional) Show detailed output log (default: false)
• -h | --help (optional) Show help text. This :)

• jq - This bash script expects to find jq as a cli tool.