@Krishna Prasad Kotti-Oracle @Dayne-Oracle

Can anyone kindly assist me with a few responses to the queries below? That would be greatly appreciated!

FDI Configuration Data Management – Key Considerations

I am keen to understand how configuration data is managed within FDI, specifically related to models, pipelines, and reports (both standard and custom-built).

Objectives & Challenges

I aim to solve two key challenges:

1. Preserving Configuration Data for Disaster Recovery
   • Ensuring we can reapply configurations in case of an incident or system failure.
2. Managing Release Promotions Across Environments
   • Understanding how to effectively promote configuration data between Dev, Test, and Prod environments.

Questions on Bundles & Automation

I recognize that there is a concept of “bundles” that encapsulates configuration data, but I need further clarity on:

• Version Control: Can we store and manage versions of configuration data systematically?
• Environment Promotions: Is it possible to migrate data seamlessly between Dev, Test, and Prod?
• Granularity of Management: Can we move specific components, or does it require an all-or-nothing migration?
• Automation Capabilities: What tools are available for automating configuration management?

Ideal Scenario – CI/CD for FDI

Ideally, I would like to implement a Continuous Integration/Continuous Deployment (CI/CD) approach using automation. This would help reduce manual intervention and minimize errors, ensuring a more streamlined process for managing and deploying configuration data

Any thoughts please ?