> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.34.0/reference/configuration.md).

# Configuration Reference

Every Terrakube service is configured with environment variables. This section lists all of them, with their defaults, for the three services you deploy:

* [API](/2.34.0/reference/configuration/api.md): database, storage, authentication, scheduler, Redis, logs, notifications, dynamic credentials, policy governance
* [Executor](/2.34.0/reference/configuration/executor.md): Terraform and OpenTofu, state and output storage, structured output, log delivery, ephemeral jobs
* [Registry](/2.34.0/reference/configuration/registry.md): modules, providers, storage, caching

Most topics have a task-oriented guide that explains *why* and *when* to change a setting; this reference is for looking up the exact name and default. Names are case sensitive.

### How to set them

| Deployment       | Where                                                                                                                                                                                |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Helm chart       | Under `env` of the component: `api.env`, `executor.env`, `registry.env`. Common settings also have chart values; see [Helm Chart](/2.34.0/getting-started/deployment/helm-chart.md). |
| Docker Compose   | The `environment` block of the service in `docker-compose.yml`, or `docker-compose/.env`.                                                                                            |
| Plain containers | `-e Name=value`.                                                                                                                                                                     |

```yaml
api:
  env:
    - name: ModuleRefreshInterval
      value: "60"
```

A variable with no default is either optional or must be provided. Secrets such as `PatSecret`, `InternalSecret` and database or storage credentials have no default and are required where the feature is used.

{% hint style="info" %}
These pages are generated from the `application.properties` of each service, so they always list every variable. The text comes from the comments in those files; a row that only says "Sets `property`" has no comment in the source. Generate them again for a release with `scripts/generate-config-reference.py`.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.terrakube.io/2.34.0/reference/configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.