> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/installation/artifacts/ansible-playbooks/initialization-playbooks.md).

# Initialization Playbooks

Rierino core platform and additional modules require a set of configurations and data sets which are applied to enabler applications

Initialization playbooks are used to populate these entries on target systems (such as saga records created on a MongoDB instance), utilizing [deployment assets](/installation/artifacts/deployment-assets.md) within the process.

<table><thead><tr><th width="188.33333333333331">Playbook</th><th>Description</th></tr></thead><tbody><tr><td>Global Helm</td><td>Extracts &#x26; defines key configuration parameters (such as URL paths) utilizing inventory and populates namespace config maps &#x26; secrets using <a href="/installation/artifacts/helm-charts/initialization-charts/global.md">global</a> helm chart </td></tr><tr><td>MongoDB Import</td><td>Imports core &#x26; module specific records into platform database, using MongoDB asset files</td></tr><tr><td>Kafka Create Topic</td><td>Creates Kafka topics with provided configuration parameters, using Kafka asset files</td></tr><tr><td>Keycloak Create Realm</td><td>Creates and configures core &#x26; module specific realms, using Keycloak asset files</td></tr><tr><td>Elasticsearch Create Index</td><td>Creates module specific indexes on Elasticsearch, using deployment asset files</td></tr><tr><td>Elasticsearch Create Synonym</td><td>Creates and uploads module specific synonym files on Elasticsearch, using deployment asset files</td></tr></tbody></table>

{% hint style="info" %}
Additional, optional initialization playbooks are also available within the deployment repository, which can be used to import configurations into systems such as Nexus, Airflow, NiFi, etc.
{% 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.rierino.com/installation/artifacts/ansible-playbooks/initialization-playbooks.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.