Feature Requests

The Harness gitops-agent helm chart has a feature to automatically upgrade itself. However, it doesn’t respect using private registries or internal proxies to DockerHub and there appears to be no way to configure it to do so. We want to be able to leverage the auto updater job while still using our private Artifactory to proxy to DockerHub to get the images.

We have a Shell Script Step that sets some output variables as secrets and we are not able to refer it in the same container step.

For pipeline Freeze window: Admin users should get a notification banner when running pipeline in freeze window same as other users. 2.Admin users better yet be blocked like normal users but then have an explicit option to bypass, similar to an approval gate or something on a CD pipeline

Two suggestions for UI improvement when editing content. Add ability to expand the Expression Box. When editing an expression the dialogue box is restricted to a single row, this makes it challenging when editing even a simple expression. In the example of an HTTP Step the Request Body could be 800+ characters which is impossible to reliably edit in the UI. Is it possible to consider adding a button to show a bigger expression dialogue box? (For example similar to how the script dialogue box can be expanded.) 2. Add (optional) word-wrap to the YAML view When using the YAML editor (on a 1920 monitor) the screen fits in ~180 characters of text. This means that continuous left-right scrolling is needed to track location. It might be beneficial if a “Word-Wrap” option were available.

Can you guys please add the Service Name as a column in pipeline executions? We have a lot of new users that do not know how to use Harness properly and this simple feature would help a lot in identifying the devs running tasks.

Google Cloud Artifact Registry (GAR) recently introduced support for generic artifact types, eliminating the need for GCS and other storage solutions for certain bundles. (See: https://cloud.google.com/artifact-registry/docs/supported-formats#generic ) As we build more native integrations with GCP, we believe that adding support for triggers based on events on Generic GAR would be highly beneficial. For Harness, it would be better to add triggers based on all types of artifacts in GCP. A few similar requests: 1) https://ideas.harness.io/feature-request/p/artifact-registry-trigger 2) https://ideas.harness.io/feature-request/p/fr-trigger-for-oci-helm-connector-google-artifact-registry

Enhancement to the existing RBAC model, specifically roles so as to restrict a user(s) ability to initiate rollback on a pipeline. This user may have execute permissions, but this request is to deny those users with rollback of specific pipeline.

I would like to be able to get more detailed pipeline event notifications in Slack, including the service name, environment, and artifact. Didn't first-gen have this?

We are intermittently getting github api rate limit error for our bot user used in harness git experience. We spoke to github support and they have given a list of all api calls made. The data shows Go-http-client/1.1 made 92.485% of the api calls and is contributing heavily to api rate limiting. Can you please provide us some feature to check the API calls done by Harness or streamline the GitExp calls to prevent the rate limit error?

The present Rancher connector is created following the document is listing the Rancher cluster project ID's which end users might not be aware of. Instead if the connector would list the display names of clusters would be much helpful as the end users would be communicating( using daily) with this names.