Environment variables

How to use

There might be a case when you need to specify environmental variables of deployed UI application by yourself, you can easily do it using TF_VAR_UI_CONFIG_VARS environment variable in GitHub Actions.

TF_VAR_UI_CONFIG_VARS uses JSON schema for specifying variables, for example:

{
    "FOO": "BAR",        // export FOO=BAR
    "FOO_TWO": "BAR_TWO" // export FOO_TWO=BAR_TWO
}

To apply changes, just commit to your repository's main branch (through PR or directly to main). If you don't have any changes, feel free to push an empty commit:

$ git commit --allow-empty -m "apply environment variables"

warning

Keep in mind that anything you'll specify manual, will override already specified/existing environment variable, for example BACKEND_API_BASE_URL is being populated by runtyme-kit, but if you manually specify BACKEND_API_BASE_URL, the end result will be your specified value.

Important

For frontend applications we should not specify any secret values as part of application configuration, since those can be easily accessed by users. Specifing secrets here might lead to data leaks and unexpected costs. We don't recommend having any secret values specified in TF_VAR_UI_CONFIG_VARS value.

UI Config variables