Create a .env file on the Viewer for every jurisdictional configuration

[emmastephenson]

What needs to be done

Add .env files for each of our pilot states:

• Tennessee
• Maine
• New Mexico
• Philadelphia

These can be kept in a separate folder called "Jurisdictional Configs" or similar.

Why it needs to be done

This will help our DevOps team when they pair with jurisdictions to ensure things are set up correctly.

Acceptance Criteria

• .env file created for each of:
• Tennessee
• Maine
• New Mexico
• Philadelphia

Technical Notes

You can refer to the Engagements Notion board to find details about each jurisdiction's setup. If you have any questions, reach out to Emma.

Additional context

Long-term, we hope to have a more robust solution for users to manage their configurations. But in the short term, this will help our DevOps team know the env vars to apply to specific jurisdictions.

[rin-skylight]

Heads up: I have concerns about this ticket. I spoke with Lina via Slack about a few of the variables...we can't necessarily enter values for everything, since Terraform generates things like connection strings at runtime. I'm also very reluctant to have any of this in publicly-accessible code, since we should theoretically have no access to these environments. By policy, we draw the support line at that stage. I would also worry that our jurisdictions may not consent to having these details anywhere open-source.

If I'm mischaracterizing this, please let me know. Otherwise, I think we need to talk over how we would want this info to be stored, and what value it brings.