Feature Requests

Our team hits the Github Rate Limit at times, and investigating these issues is time consuming. We would like Harness to please return data from the rate limit error header so that we can see 1) What account is causing the rate limit 2) What is the limit count at the time https://docs.docker.com/docker-hub/download-rate-limit/#how-can-i-check-my-current-rate For example, this information is not provided in DiND ERROR MESSAGE: GET https://index.docker.io/v2/library/docker/manifests/dind : TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

We would like to have the option to integrate GitLeaks Step in the Deploy stage of their pipelines. This would allow for the verification of any sensitive information that may be hardcoded in Terraform scripts

I want to be able to download a file previously stored in GCS from a Deployment stage. When creating a container based Step Group execution in a Deployment stage I can choose to download a file from AWS S3 and Harness File Store, but not from GCS.

Request to provide the ability/feature to submit a "dry-run" flag to harness API when creating account level templates, as a means of earlier validation.

Description: Currently, Harness applies the following search logic for filtering pipelines: Name and Tags Fields: AND logic is applied between the Name and Tags fields. Tags Only: OR logic is used when filtering pipelines using multiple tags. Customer Request: Customers have expressed the need for an AND logic when filtering pipelines by multiple tags. This would allow them to narrow down results more effectively, displaying only those pipelines that match all specified tags simultaneously. Use Case: This enhancement will be particularly useful for organizations with a large number of pipelines, where granular filtering is essential to identify pipelines with specific combinations of tags.

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.

When deploying to ECS, the deployment failed (see events below) but Harness does not detect the failure and reports the deployment as successful. We now need to add our own post-deployment checks to fail the deployment and rollback the stage, something that Harness should be doing automatically. Include task status for ECS Rolling Deployment

Option to set console view enabled for all account users by default Currently the individual users need to click on the toggle for the console view . The option to set it default for all account users is not there.

With an AWS connector set as assume role on delegate, the role has by default a timeout of 15 mins. There is a need to increase this timeout from the default of 15 min to a larger amount, say 1 hr. This is supported using an awscli command, where the duration for assume role session can be defined. Same ability to define this in the connector for assume role on delegate is needed.

Add the ability to custom message template for each event type in pipeline notification settings. Our specific focus is on slack, but this should really be supported for for any notification method such as Teams, Slack, Email, etc