Feature Requests

RSPM rules do not work for configs that are defined at github account and org level.

We'd like the ability to run the local runner as a service instead of just executing it directly while in the machine. This is to help improve uptime in case the runner goes down for any reason so we don't have to manually SSH into the machine and reboot the runner every time.

Many reports such as coverage, linters, unit tests from various languages, etc use proprietary HTML reports. Harness enables you to upload these reports as artifacts to S3 or similar, but it does not support HTML reports natively. I would like to see this feature make it to Harness similar to https://plugins.jenkins.io/htmlpublisher/ to support additional quality and build reports

We have one request to add an approval step into a CI stage that contains a simple shell script for downloading artifacts from JFrog and uploading them to S3. Since CI stages do not support approval steps in Harness, please consider this as a feature request. On the other hand, when we try to convert this simple upload-to-S3 script into a CD stage, it requires a service name and an infrastructure definition, which do not exist for this kind of task. Because these two variables are mandatory, the conversion isn’t feasible. To address this limitation, could Harness introduce a CD stage deployment type specifically for S3 uploads? This would allow such simple file-transfer workflows to be executed in CD without needing unnecessary service or infrastructure definitions.

Solution: Harness Proxy details has to be implicitly set as build args for Docker Build Plugin. Current Issue: Harness Proxy needs to be explicitly set as step output variables so that they can be set as build args for Docker Build Plugin export HTTPS_PROXY="$HARNESS_HTTPS_PROXY" export HTTP_PROXY="$HARNESS_HTTP_PROXY" export NO_PROXY="$HARNESS_NO_PROXY" This is a redundant repeatative obvious step which as an User, I do not need to add a step explicitily. Business Value: Users of the Docker Build Plugin step will have better experience and will add intelligence to the step

We have to have all of our CI stage and container step templates to run as nonroot. Though, users forget to check this option as default, creating support tickets. Requesting to allow us at the account level to default all CI stage and container step templates to default run as nonroot to True.

As a customer I want to view license utilization that excludes non-developer roles such as VPs, Directors, and Managers So that I can accurately track and validate the number of active developer licenses used on the platform. Acceptance Criteria 1) The system should provide an option (e.g., toggle or filter) to view: Developers only Non-developers only All users (default) 2) License utilization metrics should dynamically update based on the selected view. 3) Non-developer roles should be excluded from developer license counts when “Developers Only” is selected. 4) The filter or toggle state should persist across sessions for the user. 5) Admins should be able to export license data based on the selected role filter.

Currently we are running API tests post deployment and we are posting the test results in K6 so it is visible in the tests tab in the pipeline. This feature to publish test results is available only in build stage, hence we are using a build stage post deployment. if there is an API available to publish test results within harness than we can use it instead to publish tests results back to the pipeline and users can view the test results under tests tab in the pipeline

We are trying to create a deploy gitops stage, and we see that environment tag has no expression option. we would like to dynamically determine the value of environment and the gitops clusters, but it seems the option is not present.

It would be great if you a feature to create a dashboard for Artifact Signature & Verification, SLSA Attestation & Verification so that we can view the success and failure and violations in Harness pipelines at enterprise level