# Initialization Playbooks

Initialization playbooks are used to populate these entries on target systems (such as saga records created on a MongoDB instance), utilizing [deployment assets](https://docs.rierino.com/installation/artifacts/deployment-assets) 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="../helm-charts/initialization-charts/global">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 %}