Describe the bug
In the new commons config-server helm chart (release-1.3.x), the composite repository configuration variables (SPRING_CLOUD_CONFIG_SERVER_COMPOSITE_*) are hardcoded as inline value: entries directly in the Deployment pod spec. This is a regression from the older mosip-helm chart (12.0.x) where these values were correctly managed via the config-server-env-vars ConfigMap.
Additionally, the chart-managed Secret (which holds github-token- for private repos) is never referenced from the Deployment, making tokens completely ineffective even when set in values.yaml.
Affected files
helm/config-server/templates/deployment.yaml
helm/config-server/templates/configmap-env-vars.yaml
helm/config-server/templates/secret.yaml
Describe the bug
In the new commons config-server helm chart (release-1.3.x), the composite repository configuration variables (SPRING_CLOUD_CONFIG_SERVER_COMPOSITE_*) are hardcoded as inline value: entries directly in the Deployment pod spec. This is a regression from the older mosip-helm chart (12.0.x) where these values were correctly managed via the config-server-env-vars ConfigMap.
Additionally, the chart-managed Secret (which holds github-token- for private repos) is never referenced from the Deployment, making tokens completely ineffective even when set in values.yaml.
Affected files
helm/config-server/templates/deployment.yaml
helm/config-server/templates/configmap-env-vars.yaml
helm/config-server/templates/secret.yaml