Feature Requests

Currently, Harness doesn't support governance policies for GitOps resources. We'd like the ability to prohibit our users from changing the targetRevision or syncing a different ref to an existing application.

Configure the exposure of Harness Gitops Agent metrics for monitoring via Prometheus in the event of any failures on agnet. This will enable us to receive timely alerts.

i would like to run the stage group (build and deploy in QA) in parallel of a another stage that is "change management" like the photo attached (I can do it in Azure DevOps). as change mgmt is only needed in prod, but can be completed since the build process.

Would like to run end to end or regression tests as part of CD, but can't view tests tab in CD stages

I am exploring options to show some kind of a pop-up or flyer notifications to users who login to Harness tool within our enterprise. For example if we want to notify of an upcoming maintenance of the harness delegates and the downtime of it, do we have any option? I found some documentation around creating webhooks for Microsoft Teams and Slack and configuring SMTP for alerts but the functionality seems limited to pipeline alerts and would be triggered only on pipeline executions. Is there a way we can show general notifications in harness like the usecase above?

When outputting a multiline variable from a Container step, Harness behaves strangely and does not populate the variable at all. If you look at the Output tab you can see the last line of the var showing up to an empty var name.

Ability to have InputSets at project/org level to eliminate duplication and inconsistencies on updates.

Hi Team, The policies > evaluations page doesn't allow filtering by policies that resulted in a warning. It only allows filtering by Success and Failed I would like to filter based on "warning" status as well.

Today when you merge a PR, for example, that changes the pipeline configuration itself, the pipeline will trigger before the pipeline is synced with the new changes. Thus executing an old version and values for that pipeline. For this enhancement, we want that first gitX files to be synced and then the trigger will act upon them.

Have Favorite projects marked as enabled by default , so when a user logs back in Harness and clicks on project it by default shows him the favorites marked project, currently a user has to click on the favorites icon everytime to list the favorites marked projects. I’m having to constantly click the star icon every time which kind of defeat the purpose of favoriting projects. please, having an option to change the default behavior to sticky star selection would be nice. as a template designer, we switch b/t projects quite often.