Feature Requests

We have an "init" stage in our pipeline that calculates target infras dynamically based on requirements stored in Git. The stage is set as a "deploy" type because it needs to understand the service and environment, but the infra definition variable is not used. Users are required to select an infra definition, which causes confusion since it's not actually needed. We cannot use custom stage as we can pull service-related variables in it, We want to avoid hard-coding or creating dummy infra definitions.

We're trying to use the AWS Pod Identity association feature in AWS EKS, but it doesn't seem to be working. Could you please enable support for this feature?

Although configuring multiple helm charts (manifests) on a native helm service is supported as per https://developer.harness.io/docs/continuous-delivery/deploy-srv-diff-platforms/helm/native-helm-quickstart/#using-multiple-helm-charts-in-a-single-harness-service , During the execution a primary manifest has to be selected. This might benefit if the charts are different for different environments. manifestConfigurations: primaryManifestRef: <+input> However, deploying multiple helm charts when deploying a service isn't possible (The error NativeHelm deployment support only one manifest of one of types: HelmChart is noticed if the above block is removed). For instance, deploying a monitoring stack that contains multiple tools such as prometheus, grafana etc will require separate charts for the tools to be deployed. This request is for having an option to deploy all the charts from the manifest in the same service(monitoring stack) instead of having the charts deploy through separate services.

I want to use the URL from a connector. For ex, I have a non-prod and prod connector at account level, and want to use the URL as a variable from that, instead of having to create an account level variable for the URL.

I am facing an issue with Helm where arrays in values.yaml files are replaced rather than merged. This causes the appEnv array in values-2.yaml to overwrite the appEnv array in values-1.yaml. I would like a feature that allows merging of arrays in values.yaml files, possibly using tools like pyyaml, to prevent overwriting when multiple values files are specified.

Hi Team, I read your docs on generating a URL from Teams to put as part of a notification strategy in our pipelines. One thing I'm unclear on is how cutting a pasting a URL from Teams and putting it as part of the notification configuration is secure? If anyone knew the URL, wouldn't they be able to POST to our private Teams channel. Your integration with Teams doesn't provide any authentication mechanism?

Need Delegate_task_failed metric in case of script failure or error for more details

Would like expression support in a pipeline variable as runtime input where a user can select from a list of Services available in the Project. That way, when multiple Deploy stages are used in a pipeline, there's no redundancy in selecting the same Service throughout each pipeline stage. Instead, each Deploy stage's Service variable can use an expression to get the value from the new Service pipeline variable. Did not find support for this here - https://developer.harness.io/docs/platform/variables-and-expressions/harness-expressions-reference Would also like this feature expanded to Environment and Infrastructure variables.

Kindly address the SSL issues between the runner and the SMP server so users can remove the "verify_ssl false" setting for enhanced security, and additionally, update the runner to eliminate the need for executing the CP command in the run step, streamlining the deployment process.

I need the ability to synchronize deployments across pipelines. We use one pipeline per microservice, and our testing team requires the ability to synch test deployments across all microservices in order to automate regression runs/rollbacks based on regression.