Feature Requests

We're trying to use the AWS Pod Identity association feature in AWS EKS, but it doesn't seem to be working. Could you please enable support for this feature?

I would like Dark Mode so my eyes don't scorch when using the UI late at night

We have a weird stage where we need to pause the Pipeline and redirect users to our internal platform UI. I'd like to be able to set a message that everyone can use. It's pretty much saying what the stage does and a link to my own UI for them to provide an attestation/approval so I can track it. support to display a message and a HTTP URL when the pipeline is in waiting in approval state for the users who are non-approvers when they view pipeline execution.

We are requesting a native integration between Harness and Azure DevOps (ADO) Boards to automatically create work items for pipeline failures. Currently, we attempted to use Harness → ServiceNow integration for incident management, but we faced a major limitation in our operating model: Applications are supported by multiple PODs (teams) ServiceNow requires a single assignment group at ticket creation Harness does not have sufficient context to dynamically determine the correct assignment group This results in: Incorrect incident routing Manual reassignment efforts Increased MTTR and reduced operational efficiency To address this, we are moving toward using ADO Boards for failure tracking, where: Work items can be mapped to area paths / teams Ownership can be aligned more accurately with POD-based support models

I would like the ability to organize Account Level Templates in a folder structure, currently with over 330 templates it is unwieldy to use. Ability to set permissions would be ideal, but at least the ability to sort in GUI by folder would be very beneficial.

We would like to request support for write-only arguments for sensitive fields used in the harness_platform_gitops_repository resource within the Harness Terraform provider. Currently, GitOps repository authentication credentials such as GitHub PATs or SSH private keys are persisted in the Terraform/OpenTofu statefile because the provider does not support write-only attributes for these fields.

Move inline triggert entities to Git?

Currently in the native helm deployment we do not have functionality to get the helm diff to compare against the live state of the helm chart. This can be achieved using this plugin - helm plugin install https://github.com/databus23/helm-diff Please add support for the helm diff in the native helm step, as it will be more useful to understand the actual changes getting deployed.

Today, the native deployment step displays rendered manifests, apply output, and steady state output - however it does not display the pod/container logs themselves. These logs are useful for developers to debug when containers do not start up correctly, as well as serve as a longer term location for looking up them (if logs aren't forwarded right away to another provider) and the pod is deleted. It would be ideal to have the logs be shown (as an option) to the deploy type steps.

When a Harness pipeline is triggered by a Webhook (for instance Gitlab triggered the pipeline when code is committed), the pipeline executions page -> Execution Start time column currently shows the owner of the Harness API key that is used in the Webhook. It is not very useful. Instead can you display user's email who committed the code in Gitlab?.