Feature Requests

Customer wanted this functionality :- 1.Let user create a new token with the same name if the prior one is revoked. Only restrict on the same active delegate token name. Delete revoked token immediately and a new token with the same name should be allowed.

The current Notification management option at the project setting does not have an option to create a notification for selected pipelines. The only option available is for all pipelines. This enhancement request is for having the ability to specify the list of pipelines to which the notification rule will apply.

In the environments with many compliance controls in place it is safer to have only one way to manage RBAC: via user groups. So it would be very convenient to have a feature flag which disables platform functionality to assign roles and resource groups to individual users.

Currently Harness will not modify an existing webhook in GitHub when adding a trigger. This makes rotating the secret difficult. The ask here is to have a way in Harness to update an existing GitHub hook for harness with a new shared secret.

Hello Team, Can you please help us in bringing the overrides for the OPA. We want the Policy-Sets to be enforced at account level and at the same time allow exceptions to few projects. We are also aware on the workarounds but finding few difficulties in maintaining them. So, if you could help us in bringing the overrides to OPA then it will be very useful in designing the exception process in coming days.

We experienced a disruption of service using an expired Harness API key token. We want the feature in Harness to set up alerts that will alert for example two weeks ahead of the expiration of the token.

Add support for filtering the Audit Logs by Resource Type: “Variable.”

It is often the case that we need to change organizational ownership of a project and all of its resources. We can do this manually for simple projects by deleting and import yaml, etc, but I'd like to see support for doing this automatically

When adding an AWS Secrets Manager, is it possible to specify which KMS key is used for creating secrets? This will help any secrets managed by Harness and hosted in SecretsManager be accessed by other accounts.

I am often asked to provide more details on ideas which have been created by Harness based on Support tickets I've raised. I infer that Harness staff looking at the Ideas Portal are unable to link back to the ZenDesk support tickets. Currently I (the customer) am having to provide the linkage. It would reduce this dependency, and improve Harness's use of Ideas if the Harness staff could see this connection without involving the customer.