Gitops maf

[Hardik-Prajapati-10]

Issue

https://jsw.ibm.com/browse/MASCORE-10415

This change is part of enhancing Helm-based deployment capabilities by introducing a new custom resource and addon for better configuration management.

Description

Added Helm charts to define a new Custom Resource Definition (CRD): AppCfg.
Created a new GenericAddon to support dynamic configuration injection for applications.
Purpose: Enable flexible and centralized application configuration management through Kubernetes-native resources.
Impact: Improves maintainability and scalability of configuration handling across environments.

Test Results

Verified Helm chart installation on a local Kubernetes cluster.
Applied sample AppCfg resource and confirmed successful reconciliation by the GenericAddon.
Checked logs and resource status to ensure correct behavior.
Automated tests for CRD schema validation and Helm linting have passed.

⚠️ Notes for Reviewers

• Ensure you have understood the [guidelines](https://pages.github.ibm.com/maximoappsuite/playbook/tools/github/#guidelines) before proceeding with a review.
• Ensure all sections in the PR template are appropriately completed.

[whitfiea]

Why are we adding a new MAS config type rather than using the genericaddon type that already exists? https://github.com/ibm-mas/gitops/tree/main/instance-applications/550-ibm-mas-addons-config/templates

[whitfiea]

I don't think we need these image keys do we?

[Hardik-Prajapati-10]

removed.

[Hardik-Prajapati-10]

Why are we adding a new MAS config type rather than using the genericaddon type that already exists? https://github.com/ibm-mas/gitops/tree/main/instance-applications/550-ibm-mas-addons-config/templates

We are introducing a new MAS config type because the way configurations are applied differs between on‑premises and SaaS environments. For on‑premises customers, we enable the Generic Addon screen directly in the Admin Dashboard. However, for SaaS customers, these configurations are applied through saas-envs, where we define the Maximo Application Configuration Framework details. This triggers the IBM toolchain, and ArgoCD then creates the corresponding Custom Resource (CR) in the cluster.