Change configs

The changes you make to configs via the Lekko web UI or the Lekko CLI are reflected as commits in GitHub. Lekko listens for GitHub webhooks to apply changes to the current state of configs in the database.

Availability of Lekko backend

If the Lekko backend is unavailable, you cannot change the configs via the web UI and the Lekko CLI, and the changes you make to configs via Git aren't rolled out to consumers. The changes are processed after the backend recovers.

Availability of core Git operations

Core Git operations such as cloning and pushing are essential for making changes to config files. If core Git operations are unavailable, you cannot change the configs via the Lekko web UI or the Lekko CLI.

Availability of GitHub webhooks

GitHub webhooks are critical for quickly rolling out changes to configs to consumers.

If GitHub webhooks are unavailable, Lekko falls back to periodic polling. This means that changes to configs are still rolled out, but propagation time can increase.