Start from the KubeRocketCI (a.k.a. EPAM Delivery Platform) main page. This repository contains the Helm Chart templates that describe the installation of the main configuration (e.g. database registration, user creation in a database, etc.), which cannot be subsumed to the corresponding operator or allotted to the repository
Is your feature request related to a problem? Please describe.
When deploying the edp-install Helm chart, the apiGatewayUrl field in the edp-config ConfigMap is populated based on the value provided in values.yaml. If the apiGatewayUrl field is left empty in values.yaml, an empty field is rendered in the ConfigMap. However, this results in a diff in ArgoCD, causing the field to not propagate correctly to the ConfigMap. This can lead to confusion and inconsistencies during deployment.
Describe the solution you'd like
Implement a mechanism in the Helm chart to handle empty apiGatewayUrl values gracefully. If the value is empty in values.yaml, the field should either be omitted entirely from the ConfigMap or be set to a default placeholder to avoid triggering an ArgoCD diff.
Describe alternatives you've considered
Introducing a conditional check in the Helm template to exclude the apiGatewayUrl field from the ConfigMap when its value is empty.
Additional context
This issue causes unnecessary noise in ArgoCD and complicates the deployment process. A clear resolution will help maintain a smooth CI/CD pipeline.
Is your feature request related to a problem? Please describe. When deploying the
edp-installHelm chart, theapiGatewayUrlfield in theedp-configConfigMap is populated based on the value provided in values.yaml. If theapiGatewayUrlfield is left empty in values.yaml, an empty field is rendered in the ConfigMap. However, this results in a diff in ArgoCD, causing the field to not propagate correctly to the ConfigMap. This can lead to confusion and inconsistencies during deployment.Describe the solution you'd like Implement a mechanism in the Helm chart to handle empty
apiGatewayUrlvalues gracefully. If the value is empty in values.yaml, the field should either be omitted entirely from the ConfigMap or be set to a default placeholder to avoid triggering an ArgoCD diff.Describe alternatives you've considered Introducing a conditional check in the Helm template to exclude the
apiGatewayUrlfield from the ConfigMap when its value is empty.Additional context This issue causes unnecessary noise in ArgoCD and complicates the deployment process. A clear resolution will help maintain a smooth CI/CD pipeline.