Feature Requests

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.

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 KMS connector only accepts KMS AR stored in Harness Secret Manager. We need an ability to pull those ARN from AWS secret manager.

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.

Currently, if a user makes any changes to a Secret Manager Template, they must edit the Custom Secret Manager and re-select the updated template to reflect the changes. We would like to automate the reconciliation of Secret Manager Templates as we frequently make changes to them.

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.

Hi Team, We would like to ephemeral-storage setting exposed for helm charts as most of the autopilot clusters set a default limit of 1GB, which is difficult to modify, if this value is exposed for helm charts it would be easier to deploy delegates and not run into errors.