What needs to be done

Based on the value of one configuration name environment variable, choose a collection of environment variables to set on application startup.

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

• collections created for each
  • AWS integrated
    • APP_ENV=test
    • NEXT_PUBLIC_NON_INTEGRATED_VIEWER=false
    • SOURCE=s3
    • METADATA_DATABASE_TYPE=undefined
    • METADATA_DATABASE_SCHEMA=undefined
  • Azure integrated
    • APP_ENV=test
    • NEXT_PUBLIC_NON_INTEGRATED_VIEWER=false
    • SOURCE=azure
    • METADATA_DATABASE_TYPE=undefined
    • METADATA_DATABASE_SCHEMA=undefined
  • AWS non-integrated
    • APP_ENV=prod
    • NEXT_PUBLIC_NON_INTEGRATED_VIEWER=true
    • SOURCE=s3
    • METADATA_DATABASE_TYPE=sqlserver
    • METADATA_DATABASE_SCHEMA=extended
  • Azure non-integrated
    • APP_ENV=prod
    • NEXT_PUBLIC_NON_INTEGRATED_VIEWER=true
    • SOURCE=azure
    • METADATA_DATABASE_TYPE=sqlserver
    • METADATA_DATABASE_SCHEMA=?
• Setting the new configuration name environment variable causes the correct set of environment variables to be set on startup

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.