Feature Requests

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.

When configuring the Values.yaml for a service, it is possible to configure either the path to the Values.yaml or the folder containing Values.yaml. Multiple entries can be created for separate values.yaml. However, specifying " " wildcard to fetch all the values files isn't supported and .yaml would be treated as a file name. This request is to have the support for wildcard listing and using multiple Values.yaml with the use of wildcards that would match with the file names. It would benefit the cases where the value.yaml files are dynamic and if they are constantly being added/changed on the repo. Currently during the deployment *.yaml is treated as a file name and the deployment fails because such a file does not exist

The slack integration for pipelines doesn't offer any customization in terms of what information is included. It would be very useful to be able to select what fields to include or not. At the very least, I feel like the slack messages should include identifying information for the artifact that a pipeline is deploying

Value replacement secret injection, ie: the ability to supply a value within the ArgoApplication of something like <@dynatrace_apikey> that would autoinject a secret into the application from another secret management engine (like Vault)

While typing details for creating a support case, the details are deleted if a user accidentally closed the tab. The user has to re-enter the details again. This has also been noticed across modules in harness where there is no warning when clicking off of them and until the user realises they have lost everything they just typed or configured. Having some sort of a warning or having these details auto saved shall help remove the toil of rentering again.

How to populate the value of Variable B based on the value of Variable A in a Harness Variable A: The value of Variable A uses <+input> to allow user input. allowedValues restricts the input to predefined options like Option1, Option2, and Option3. Variable B: The value of Variable B is determined dynamically based on the value of Variable A using Harness's expression language. Logic: If Variable A is Option1, then Variable B is set to ValueForOption1. If Variable A is Option2, then Variable B is set to ValueForOption2. If Variable A is Option3, then Variable B is set to ValueForOption3. The else block provides a fallback value if none of the conditions are met.

We'd like the ability to call UI Actions in ServiceNow from Harness. There is a method that UI Actions can be called using ServiceNow's REST API https://servicenowthink.wordpress.com/2019/01/07/how-to-call-any-ui-action-with-rest-api-or-ajax-servicenow/ We have Change Request records where we need to use UI Actions in order to create approvals or move the Flow along. This would help with our automation so the user doesn't have to go back to ServiceNow and manually click these UI Actions.

Currently, Harness doesn't provide a way to see what version of the artifact is deployed in 'View in table' screen (pop-up window) for TAS artifacts. It list out 'Service', 'Artifact', 'Infra/Gitops cluster' and 'Instances'. It doesn't provide other details like artifact version, and date/time of deployment. Detailed view of what's currently deployed in environment for all the components is very helpful for various scenarios.

As it stands there's not any built-in YAML validator on harness, similar to the Gitlab pipeline validator ( https://docs.gitlab.com/ee/ci/pipeline_editor/index.html#validate-ci-configuration ) that's baked into their editor. This becomes a problem when a pipeline fails because of invalid YAML in a subsequent stage after an hour and a half of execution. Please add automated validation of the YAML in the pipeline editor, and please at least add an option to immediately fail a pipeline for invalid YAML.

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?