Konfiguracja

Config seed, miejsce przechowywania konfiguracji, git i ytt

  1. Przykład
  2. Skąd odczytywany jest config.yaml
  3. Zmienne

Zmień je, aby zdecydować, skąd pochodzi konfiguracja: z config seed, bazy danych, gita lub szablonów ytt.

Przykład

Zastosuj zamontowany config seed, sprawdzaj go co pięć minut i trzymaj config.yaml w bazie danych. W docker-compose.yml:

    environment:
      - CONFIG_SEED_PATH=/seed/seed.yaml
      - CONFIG_SEED_RELOAD_SECONDS=300
      - ENABLE_CONFIG_IN_DATABASE=1
      - ALLOW_ENV_EDIT=0              # the environment is declared here, not on the settings pages
    volumes:
      - ./seed:/seed:ro

Nieprawidłowy seed nie pozwala serwerowi się uruchomić. Format pliku opisuje Config seed.

Skąd odczytywany jest config.yaml

Kategorie, role i stałe pochodzą z config.yaml na dysku lub z jego kopii w bazie danych, o czym decyduje ta kolejność:

  1. ENABLE_CONFIG_IN_DATABASE, gdy jest ustawiona, w środowisku lub na karcie Konfiguracja strony ustawień: 1 odczytuje bazę danych, 0 odczytuje plik.
  2. W przeciwnym razie źródło konfiguracji zapisane w bazie danych (file lub database), które instancje skonfigurowane przed wersją 6.3.0 wybrały na stronie ustawień.
  3. W przeciwnym razie plik: config.yaml repozytorium z włączonym Używać do konfiguracji?, a jeśli takiego nie ma, repozytorium z włączonym Używać do formularzy?, a jeśli i takiego nie ma, ten z CONFIG_PATH.

Jawnie ustawiona ENABLE_CONFIG_IN_DATABASE zawsze wygrywa, nawet 0 z zapisanym database. Jest odczytywana przy każdym wczytaniu konfiguracji, więc zmiana działa bez restartu. Strona Stan pokazuje używane źródło na karcie Informacje.

Zmienne

Każda zmienna tej grupy, z typem, wartością domyślną i opisem:

Zmienna Opcje/Wartości domyślne Komentarze
CONFIG_SEED_PATH
string
added in version 6.3.0
Domyślnie:

Config seed file
a valid file path

Path to a declarative config seed. When set, the yaml file it points to is applied at startup and the admin objects it declares become read-only in the interface, so a whole instance can be rebuilt from git on an empty database. Secrets are referenced as ${ENV_VAR} and resolved from the environment, so the file itself holds none. Unrelated to CONFIG_PATH, which holds the forms configuration. An invalid seed makes the server refuse to start, and so does a path whose file is missing (a mounted file may only be late). Leaving it empty turns the seed off: the next start releases every object an earlier seed made read-only, keeping its values, so it can be changed in the interface again. See the Config seed page in the documentation.
CONFIG_SEED_RELOAD_SECONDS
integer
added in version 6.3.0
Domyślnie:
60

Config seed reload interval (seconds)
0 or a number of seconds

How often the config seed file is checked and re-applied when its content has changed, in seconds. This is what lets a seed edited in git take effect without restarting: on kubernetes a ConfigMap is remounted under the running pod within about a minute and the change is picked up from there. A reload that fails is never fatal, unlike the one at startup: the configuration already in force is kept and the Status page reports it. Set it to 0 to check only at startup, leaving POST /api/v2/config-seed/apply and SIGHUP. Takes effect at once, without a restart. Ignored when CONFIG_SEED_PATH is empty.
ALLOW_ENV_EDIT
boolean
added in version 6.3.0
Domyślnie:
1

Allow editing these settings
0, 1

Whether the settings pages may write persistent/.env. Set it to 0 in a declarative deployment (kubernetes, docker-compose, ArgoCD): there the file is either ephemeral, so a save is silently lost at the next restart, or durable, so it drifts away from the manifest that is meant to be authoritative. With 0 every variable is shown with its value in force but cannot be changed, and the save endpoint refuses.
ENABLE_CONFIG_IN_DATABASE
number
added in version 6.1.0
Opcje:
  • 0 (domyślnie)
  • 1

Store the configuration in the database
0, 1

If you use git repositories to store the forms, you can choose to store the master config.yaml in git as well.
Or, you can choose to have the config.yaml in the database instead. Having a clean separation: master config.yaml in database, and the actual forms in git.

This gives the config.yaml in the database the highest priority in the loading order.
GIT_CLONE_COMMAND
string
added in version 6.0.2
Domyślnie:
git clone

Git clone command
a valid git clone command

The command used to clone git repositories. Note that branch and repository will be auto added.
GIT_PULL_COMMAND
string
Domyślnie:
git pull

Git pull command
a valid git pull command

The command used to pull git repositories. Note that branch and repository will be auto added.
GIT_PUSH_COMMAND
string
Domyślnie:
git push

Git push command
a valid git push command

The command used to push git repositories (used by the designer’s sync to git feature). Note that -u origin HEAD will be auto added.
USE_YTT
number
added in version 5.0.2
Opcje:
  • 0 (domyślnie)
  • 1

Enable the ytt interpreter
0, 1

https://github.com/carvel-dev/ytt is a tool for yaml templating. It can be activated by this variable.
YTT_ALLOW_SYMLINK_DESTINATIONS
string
added in version 5.0.8
Domyślnie:

ytt allowed symlink destinations
valid paths

Ytt disables templating with symlinks by default. If you want to allow symlink use on specific directories, this variable can be set to the path(s) where the symlinks are allowed (multiple paths separated by Node’s path.delimiter). Note: enabling this may come with some risks, see ytt FAQ for more info.
YTT_DANGEROUS_ALLOW_ALL_SYMLINK_DESTINATIONS
number
added in version 5.0.8
Opcje:
  • 0 (domyślnie)
  • 1

ytt dangerous allow-all symlink destinations
0, 1

Ytt disables templating with symlinks by default. If you want to allow all symlink use EVERYWHERE, you can set this variable to 1. Note: enabling this comes with some risks (hence the ‘DANGEROUS’ part), see ytt FAQ for more info.
YTT_VARS_PREFIX
string
added in version 5.0.8
Domyślnie:

ytt vars prefix
a valid prefix

Environment variable prefix for ytt to get data values from. For example, when set to MY_PREFIX, MY_PREFIX_my_var=value results to the ytt data value my_var=value.
YTT_LIB_DATA_{dynamic}
string
added in version 5.0.8
Domyślnie:

ytt lib data
a valid lib data value

This is not a single variable but rather an infinite amount of variables. You can set as many as you want. The dynamic part is the name of the lib data. For example YTT_LIB_DATA_MYLIB=values.yml results in the contents of values.yml to be used by ytt in the mylib library.