You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we expect that the variables DOMAIN and ENV are set and all other config values are potentially affected by what these are set to. Loading of config overrides is done using these 2 values like so:
/config/domains/{DOMAIN}/{ENV}.config.json
At Finn, we use the environment FIAAS_ENVIRONMENT which roughly equates to the expected ENV. There's currently no clear place that one might map FIAAS_ENVIRONMENT to ENV. Ideally, infrastructure would set the ENV but in cases where that's not practical, how should we suggest this be handled?
set ENV to = FIAAS_ENVIRONMENT in a bash script
set it in code somewhere?
make it possible to configure the name of the ENV and DOMAIN env var names?
something else?
The text was updated successfully, but these errors were encountered:
Currently, we expect that the variables DOMAIN and ENV are set and all other config values are potentially affected by what these are set to. Loading of config overrides is done using these 2 values like so:
/config/domains/{DOMAIN}/{ENV}.config.json
At Finn, we use the environment FIAAS_ENVIRONMENT which roughly equates to the expected ENV. There's currently no clear place that one might map FIAAS_ENVIRONMENT to ENV. Ideally, infrastructure would set the ENV but in cases where that's not practical, how should we suggest this be handled?
The text was updated successfully, but these errors were encountered: