Feature Requests

We have scenario about repositories type - infra that this repos not exist backend file tf cause this file's buiding in runtime pipeline in github action, we've including this file in runtime before to start terraform plan and apply.

Harness RBAC should allow restricting access to the Events and Logs within the Resource View. The underlying ArgoCD allows this via their RBAC, but it'd be nice if we could restrict access via Harness roles so we could get finer grained control: Some operators only need access to see the health of a resource, not the logs.

I would like to request the ability to publish test reports from a Run step within a Custom Stage or Step Group. These types of stages are used to execute QE automation scripts and will provide a lot of benefits for viewing results and providing summary of state of automation test runs.

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?

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?.

Currently only for pipeline entities, gitconfig is available for policy evaluation. The feature request is to make this available for all entities backed by git manifest. This will allow use cases such as "disabling direct commits to main branch" or allowing pushes only on feature or release branches.

Developers many times reject the manual approval without any reason. We want to know why developers decided no for manual approval. This information is crucial for us to know why the pipeline failed. If we know the reason, then we can try to automate and make sure there is no need for manual approval.

If there are multiple user groups and I require approval for each of them, there should some option like this. Right now I do not find any approach for this

Allowing only specific versions of services to deploy on Prod/Cob pipelines. This would help us to control deployments on production. Something that could help us mark specific versions eligible for deployment on Prod/Cob.

Issue Description: When attempting to copy or download console log output, the timestamps are not included in the copied or downloaded content. Request: Please enable the ability to copy console logs along with their timestamps. Additionally, when downloading console logs, the timestamps should be preserved and visible in the downloaded output.