Feature Requests

Give preference to usr/bin for third party tool or provide a way to set path variable

https://developer.harness.io/docs/platform/delegates/manage-delegates/configure-delegate-proxy-settings/#kubernetes-delegate-proxy-settings Based of this above document only user name and password auth is enabled for proxy. JPMC would like to have Kerberos Auth enabled.

Currently audit streaming does not work for an s3 bucket that has versioning and object lock enabled with retention “compliance” mode. This causes the below error when streaming the audit logs to s3 com.amazonaws.services .s3.model.AmazonS3Exception: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters (Service: Amazon S3; Status Code: 400; Error Code: InvalidRequest; Request ID: EPG03R1J2VACB0WQ; S3 Extended Request ID: YG4XRMK8/umXDbJRQ39MBv6bJrDBQzUeAGmg+0B+l/HVnscKSp9pwUxDG0099gaZu5lStLqPfG3Fg5WHMStkfg==; Proxy: null) This request is to add support to the audit streaming with this mode.

Description: Requirement to set a Time-To-Live (TTL) on a delegate token while managing delegates using Terraform. Currently, our Terraform provider does not support any parameter that allows configuring TTL for delegate tokens. Requested Enhancement: Introduce a configurable parameter in the Terraform provider to allow users to define a TTL for delegate tokens during delegate creation or update.

Often times I'm working in a specific area/module within the product and I need to repeatedly search for different things in the docs. For each search, I need to go and specify the module filters to narrow down the results to only the area/modules I'm working on. It would be a much better experience to have the module filter persist so that I can search repeatedly and relevant/filtered results without having to manually re-filter every single time.

User wanted to make notification method configurable so this will significantly improve usability. because at this moment, when configuring pipeline notifications, the notification method is not configurable, which is very rigid and forces all development team to stick to the same notification mechanism.

We need to provide the ability to import secrets from the external secret managers and create them as reference secrets in Harness ... Also, the ability to Periodically check for new secrets and create them in Harness On-demand import of new secrets

https://support.harness.io/hc/en-us/requests/58707?page=1 As per the discussion in thread, we at JPMC dont want to disable sending logs to Harness, as well we cant open connectivity to logging.googleapis.com and dont want to see the error logs in all our delegates which makes our lives difficult to find the log that we want. Please help with an implementation that helps with logs getting to harness and not seeing those tons of exceptions in the log.