Feature Requests

FIS global has requested to support user group in E-Mail Step. This will help them to provide the user group for sending E-mails instead of manually adding all the users.

We'd like the ability to trigger multiple pipelines with a single webhook event. In our case, we have multiple input sets for each service deployment we want to do. When a webhook is sent to Harness, we want Harness to trigger 1 pipeline per input set. We also don't want to configure multiple triggers for this since it will add redundancy and make debugging triggers difficult.

Hi, We are seeing that whenever we made change to harness org level templates, we have to ask consumers to reconcile it manually for every single pipeline, please enable bulk-reconciliation-of-templates: https://developer.harness.io/docs/platform/templates/reconcile-pipeline-templates/#bulk-reconciliation-of-templates Thanks, Sohel

Currently, AIDA adoption metrics are not available in real-time or near real-time, nor are they accessible from the client side. This limits our ability to track usage effectively and creates dependency on Harness Support for visibility. Additionally, the metrics are aggregated and do not provide insights at the individual AI feature level. This makes it difficult to understand which features are performing well and which need improvement in terms of adoption. Request: 1) Provide client-side access (dashboard or API) to AIDA adoption metrics. 2) Enable real-time or near real-time metric updates. 3) Offer granular breakdowns of adoption by individual AIDA features (e.g., Harness support, Dashboard Intelligence, pipeline failure recommendations, etc.). 4) Include trend and historical usage analysis. Impact: 1) Having access to real-time, granular AIDA metrics will: 2) Allow us to optimize AI feature usage and drive targeted adoption. 3) Enable internal stakeholders to monitor and improve team productivity. 4) Reduce dependency on Harness Support for data access. 5) Support continuous feedback loops for AI feature enhancements.

When we use filter lists of environment or infrastructure while running the pipeline, the infrastructure defination is not present in the compiled yaml, due to this it is hard to implement OPA policy on it. Please add infrastructure definations as well in compliled yaml incase of filtered list.

We'd like to request HTTP matching for Canary Traffic Routing configuration. Currently, Harness only supports routes but we would like Harness to support URI matching as well. For example, http: - match: - uri: prefix: /api/v1/

Due to the CD Pipeline failing due to a SOPs decryption issue, the only way to achieve the runtime decryption of secrets.yaml in the current design is to include the SOPs-related file as part of the chart itself. This will ensure it's downloaded with the manifest file and available in its dedicated folder, preventing conflicts with other executions. Customer repositories maintain override secrets.yaml files outside the charts directory. There's no option today to download the override files into a uniquely identifiable folder. This request is to download override files such as secrets.yaml into a unique isolated directory. This feature request is important for enabling the customer team to begin using Harness pipelines in production and to validate the workflow thoroughly in lower environments ahead of the production rollout.

We'd like for the GitOps pod logs to support ANSI color codes

For container Run step, use the image entrypoint defined in the dockerfile instead of requiring shell and command fields. This works only for background step at the moment. It would be useful for Run steps as well. The use case is to run some tests where the image is already set up to run them. It should be blocking (not background) since it is for running smoke tests.

Hi, As we are moving from bitbucket pipeline to harness, in bitbucket we have an option to remove the older cache from the pipeline. In Harness pipeline also we want to remove older cache. We have enabled our cache intelligence in harness pipeline build stage. Now we want to remove older cache from harness pipeline. Please guide us on this