Creating Environment Variables

Creating Environment Variables

Creating new environment variables is a multi-step process as secret variables are stored as environment variables, forcing us to git ignore our .env file.

Add variable(s) to .env

• Make sure that the variable(s) you are adding does not already exist in the .env file
• If it doesn't already exist, add the variable(s) to the end of the .env file in the format <VARIABLE_NAME>=<value> (Ex. EXAMPLE_VAR=testing)
• Update .env.example with the name of your new variable(s) in the format <VARIABLE_NAME>= (Ex. EXAMPLE_VAR=)
• Keep in mind that the .env file is NOT supposed to be committed, while the .env.example file is

Update Google Drive

For others to access your new variable(s) when setting up their dev environment, you need to update the shared .env file in Google Drive

• Login to Google Drive with [email protected]
• Navigate to the 'Secret Files' folder inside of the 'Development' folder in the 'Feedback Survey Automation' folder in Drive
  • Replace the .env file with your local copy
• If your new environment variable(s) is needed for production runs, navigate to the Production 'Secret Files' folder inside of the 'Production' folder in the 'Feedback Survey Automation' folder in Drive
  • Replace the .env file with your local copy (Make sure your .env file has been updated with existing production environment variables first!)

Update GitHub Secrets

Many of the GitHub Workflows need access to the environment variables defined in .env. Be sure to update the DEV_ENV secret and, if needed, the PROD_ENV secret with your new environment variable(s).

Post on Slack

Posting a message on the Hack4Impact Slack channel will notify others that they need to update their .env files with the new variable(s).