Feature Requests

Do you know when we can expect to see the Apply step console output that would show the output of DML commands that got applied, would be nice to have this output available in a log for reference, currently we only see a summary at the end, which lists the rows effected and changesets applied. planned approch: allow passing in the log-level and log-file commands to increase logging granularity, and output additional log detail to a file.

The infrastructure view of Pipeline Studio opens by default after clicking Edit Pipeline. When working on a pipeline, you want to edit it repeatedly after getting feedback from a run. Once you click Edit Pipeline, the Pipeline Studio opens but shows the Infrastructure view, which can be changed sometimes, but you generally want to keep it the same. I'd rather have the Execution view shown by default.

Upgrade MacOS image Xcode 16.3 for CI builds

Wanted GitOps application set template configured to include the functionality like argo-cd application supports multiple sources such as helm from one repo and the values files from a different repo. The manifests is deemed invalid when spec.source is missing and spec.sources is provided instead.

Dashboard for listing all the components across the all projects so that user can search for components at account level and a dashboard for listing all pipelines that have SBOM component violations

User would like to the failure strategy to retry a stage if a step or step group fails. Currently, only option is to rollback the stage if a step fails. would like to see the option to retry the entire stage if a step within the stage fails.

The ability to leverage Github Actions directly in Harness is a HUGE accelerator. Currently they are only supported in Cloud infrastructure due to the pre-requisites needed to be installed on the VM. These should be made available for self-managed VM build infrastructure as well, assuming the pre-requisites are published and can be installed and setup on the VM.

Currently, if you have common utility code in your OPA policy, you have to copy and paste it across all of your policy documents to use it. This is not DRY and can potentially lead to lots of unfortunate failures in policy enforcement if this code is updated frequently / in lots of different places and something is missed. It would be nice if common policy code could be stored in a library and imported into the main policy documents.

Currently, Test Intelligence does not work with pytest-xdist. We would like to see support for this

When setting up notification for pipeline it should have option to customization such as adding detailed information to the notification body, author needs to tag on message etc.. For example, n the event of a failure, you can tag the PR author, customize the message body, and post to the Teams channel.