Publishing Helm Chart v1.0.1 with support for Azure Ingress Controller.

Author: hdphelm

charts/hybriddatapipeline/ReadMe.txt

@@ -0,0 +1 @@
+Review the EULA at: https://www.progress.com/legal/license-agreements/datadirect

charts/hybriddatapipeline/eula.txt

@@ -91,7 +91,7 @@ spec:
               value: /app
           {{- end }}
             - name: ACCEPT_EULA
-              value: "true"
+              value: "{{.Values.hdp.eula.accepted}}"
             - name: HDP_ADMIN_PASSWORD
               valueFrom:
                 secretKeyRef:

charts/hybriddatapipeline/templates/haproxy-ingress.yaml

@@ -7,6 +7,7 @@ tests:
   - it: should render the statefulset with the correct release name and service name
     set:
       hdp.services.hdpService.name: "hdp-service"
+      hdp.eula.accepted: "true"
       hdp.replicaCount: 3
       hdp.updateStrategy.type: "RollingUpdate"
       hdp.image.repository: "my-repo"

charts/hybriddatapipeline/templates/statefulset.yaml

@@ -5,6 +5,13 @@
 ## @section hdp The parameters for configuring the Hybrid Data Pipeline (HDP) server. The Hybrid Data Pipeline Helm chart is used to deploy the HDP server as a Kubernetes pod in a Kubernetes cluster.
 ##
 hdp:
+  ## This section manages the End User License Agreement (EULA) acceptance.
+  ## Setting 'accepted: true' indicates that you have read and agreed to the EULA.
+  ## Failure to accept the EULA may result in deployment failure.
+  ## you can review EULA here: https://www.progress.com/legal/license-agreements/datadirect 
+  eula:
+    accepted: "false"  # Indicates explicit acceptance of the EULA. Set to "true" to proceed. Review the EULA before accepting.
+    
   ## @param hdp.replicaCount The number of HDP server nodes to be deployed
   ##
   replicaCount: 2