Feature Requests

Changes made directly in Github do not go through any validation. Harness only validates pipeline changes done through Harness UI. If we are to make a change to 300+ pipelines via Github, there is no way to run this validation right now. Request is to expose Harness validation API or build a feature where users can easily validate their feature branches.

UI or API to allow owner of Harness accounts to see how much is used of the Harness Platform limits documented here - https://developer.harness.io/docs/platform/account-license-limits/

We have platform limit as documented here https://developer.harness.io/docs/platform/account-license-limits/ . Need to show alerts on account when ever the limit is nearing.

Raising a feature request to enable support for using Harness AIDA to create templates. Currently, AIDA can assist with creating pipelines, but it does not support the creation of reusable templates directly. CapGroup has asked for guidance on using AIDA to create templates, and since there is no existing documentation or functionality for this, it highlights a gap in the current experience. Enabling AIDA to assist with template creation would significantly enhance usability, especially for organizations relying on standardized, repeatable workflows, and would align with the broader goal of making pipeline management more intuitive and AI-driven.

Hi, we need to have the branches dropdown in the harness pipeline input sets. But for now, we don't have that option.

Please provide an option to configure the Baseline so that it is set only on the first successful scan of the master/main branch. Currently, the Baseline is updated after every successful scan on master/main, which causes net new vulnerabilities to disappear from subsequent scans since the Baseline keeps shifting. As a result, builds are not being gated by new vulnerabilities, because each new successful scan resets the Baseline and removes the visibility of net new issues in following builds. This dynamic updating prevents us from blocking builds based on newly introduced vulnerabilities, which is a key requirement for our process.

Currently, the GSM connector only supports pulling secrets from 1 project. This means that if our secrets are spread across 100 projects, we need to create 100 connectors. Just how multi-project OIDC support for GKE + Cloud Run was released, please add this feature to Google Secret Manager plugin too. GKE : https://developer.harness.io/docs/continuous-delivery/deploy-srv-diff-platforms/kubernetes/define-your-kubernetes-target-infrastructure/#enable-cross-project-access Google Cloud Run: https://developer.harness.io/docs/continuous-delivery/deploy-srv-diff-platforms/google-cloud-functions/google-cloud-run/#enable-cross-project-access

For the tag values in dashboard the tag values don't update when in the folder. This means you can filter by tags that don't exist in a folder. This isn't a great experience for end users

I'd like to be able to inspect the exit code of a step to determine if it should exit failure or warning. Some script-based validations are desired for warnings, and some are desired for blocking. Being able to detect via exit code would allow more flexibility in this regard, similar to this gitlab feature: https://docs.gitlab.com/ci/yaml/#allow_failureexit_codes

Need a API to get Input parameters from last successful pipeline execution of the service in given environment. After Production deployments are done. we will backfill hotfix environments. We have Automation to back fill the hotfix environments. Please provide API to get the Input parameters.