Feature Requests

Currently, when a policy fails, we display the following default message: The following Policy Set was not adhered to: <my custom message>. However, I would like to remove the phrase "The following Policy Set was not adhered to:" from the message and simply display the following: <my custom message> Additionally, it would be helpful to support custom messages and hyperlinks in the failure message.

Currently the only configuration for wait step is providing time duration. This enhancement request is for having option to provide more dynamic options like a cron expression or the ability to provide certain day of week e.g wait until next Tuesday.

Feature request as suggest by Harness team to enable system level error retry mechanism for the below failures : - Pod eviction Failure to connect to addon client Connectivity errors between delegate and ci lite engine ref : https://support.harness.io/hc/en-us/requests/72479?page=1

Feature request to natively support the accordion functionality in the Backstage and React JSON Schema Form (RJSF).

We would like the option to select GCP in Infrastructure Type when using SSH Deployment Type.

We have templates that are used in prod-2 and prod-3 Harness, and have to select the url we use, ( app.harness.io vs app3.harness.io ), in scripts using the account id. I'd like an expression, (for example <+account.base_url>), that will provide the correct base url for whichever Harness instance the template is running in

Is there a way to freeze (prevent execution) of custom stages and CI stages as part of a freeze window? We have many pipelines which leverage these custom stages as part of deployments. Additionally, we sometimes need to freeze builds.

Currently, GAR (Google Artifact Registry) is not available as an option in WinRM/SSH Type Deployment. Could you please add support for this feature? Beyond Docker and Maven, additional package formats such as npm, Python, Apt, Yum, Kubeflow Pipelines, and Go are also supported in GAR and are no longer in Pre-GA.

Currently, the inventory dashboard relies on APIs, which do not retain historical data on volumes attached to EC2 instances and this limits visibility into past volume associations. We would like to explore whether CUR data includes historical records of volumes attached to EC2s. If such data exists, can we create a new dimension that exposes this information for better tracking and analysis?

Hello Team, We would like to request the activation of the PL_CUSTOM_BANNERS feature for our Harness account. Thank you!