From 62c3afe293cc6adf5a49512c95f5d48a433f683a Mon Sep 17 00:00:00 2001 From: Vaibhav Pathak Date: Wed, 11 Feb 2026 15:18:51 +0530 Subject: [PATCH] fix --- .../workflow-template.yaml | 55 ++++++++++--------- 1 file changed, 30 insertions(+), 25 deletions(-) diff --git a/environment-provisioner/workflow-template.yaml b/environment-provisioner/workflow-template.yaml index b17cf8b..1ef8e73 100644 --- a/environment-provisioner/workflow-template.yaml +++ b/environment-provisioner/workflow-template.yaml @@ -342,35 +342,40 @@ spec: done fi - # Initialize INLINE_VALUES with ingress annotations - # Dotted annotation keys (like nginx.ingress.kubernetes.io/ssl-redirect) must use - # the values block, not parameters. Helm's --set interprets dots as nested paths. - INLINE_VALUES=" - values: | - ingress: - annotations: - nginx.ingress.kubernetes.io/force-ssl-redirect: \"true\" - nginx.ingress.kubernetes.io/ssl-redirect: \"true\" - cert-manager.io/cluster-issuer: letsencrypt-prod" - - # Check for edited values content - merge with base annotations + # Check for edited values content and create separate values files + # Using separate files avoids YAML indentation issues with inline values blocks EDITED_CONTENT=$(echo "$VALUES_CONTENT_EDITS" | jq -r ".\"$service\" // empty") + EXTRA_VALUES_FILES="" + if [ -n "$EDITED_CONTENT" ] && [ "$EDITED_CONTENT" != "null" ]; then echo " Writing edited values content to override file..." - # Write the edited content to a values override file VALUES_OVERRIDE_FILE="values-override-${SANITIZED_SERVICE}.yaml" - echo "$EDITED_CONTENT" > "manifests/$VALUES_OVERRIDE_FILE" + + # Write ingress annotations + user edits to a single file + cat > "manifests/$VALUES_OVERRIDE_FILE" < "manifests/$INGRESS_FILE" <