LogoLogo
Home
Installation
Installation
  • Introduction
  • Deployment Alternatives
    • Kubernetes Deployment
      • Prerequisites
      • Recommended: Helm - Fully Automated
      • Alternative 1: Ansible - Fully Automated
      • Alternative 2: Ansible - Step-by-Step
      • Cloud Specific Details
    • Sandbox VM Deployment
      • AWS AMI - Developer Lite
    • Local Test Deployment
  • Artifacts
    • Helm Charts
      • Umbrella Charts
        • Ready Core
        • Ready CMS
        • Ready PIM
      • Initialization Charts
        • Namespaces
        • Global
        • Loader
        • Deployer API
        • Deployer
      • Application Charts
        • Admin UI
        • Gateway
        • Spring Runner
        • Samza Runner
        • Socket Runner
        • Storefront
      • Batch Charts
        • Cron
        • Job
      • Deprecated
        • Authentication
        • Session
        • H2O Wave
        • Wave App
    • Deployment Assets
      • Deprecated
    • Docker Repository
      • Front-end Images
      • Back-end Images
      • Python Images
    • Maven Repository
      • Core Packages
      • Runner Packages
      • Processors Packages
      • Custom Packages
      • Gateway Packages
    • Python Packages
    • Terraform Configurations
    • Ansible Playbooks
      • Initialization Playbooks
      • Application Playbooks
      • Enabler Playbooks
  • Administration
    • Cost & License Management
    • Secrets & Config Management
    • Testing & Health-Check
    • Logs & Traces & Metrics
    • Backup & Recovery
    • Technical Support
Powered by GitBook

© Rierino Software Inc. 2025. All rights reserved.

On this page
  1. Artifacts
  2. Ansible Playbooks

Initialization Playbooks

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

PreviousAnsible PlaybooksNextApplication Playbooks

Last updated 6 months ago

Initialization playbooks are used to populate these entries on target systems (such as saga records created on a MongoDB instance), utilizing within the process.

Playbook
Description

Global Helm

Extracts & defines key configuration parameters (such as URL paths) utilizing inventory and populates namespace config maps & secrets using helm chart

MongoDB Import

Imports core & module specific records into platform database, using MongoDB asset files

Kafka Create Topic

Creates Kafka topics with provided configuration parameters, using Kafka asset files

Keycloak Create Realm

Creates and configures core & module specific realms, using Keycloak asset files

Elasticsearch Create Index

Creates module specific indexes on Elasticsearch, using deployment asset files

Elasticsearch Create Synonym

Creates and uploads module specific synonym files on Elasticsearch, using deployment asset files

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.

deployment assets
global