Feature Requests

When you add a description to a runtime variable and then when you run the pipeline it only shows the description to the user when you hover over the below icon , which isn’t obvious. Can the UI be changed to make the description show to the user without the need to hover over any icon

I want to use the AWS connector permission in S3 cache/restore step to access S3 however S3 cache/restore step is currently using the permission on the stage infrastructure connector. Expected behavior: When we specify an AWS connector in the S3 cache/restore step, we need to use the permission of AWS connector to access S3 rather than using the permissions defined in the stage infrastructure connector Observed behavior: In order to access S3 currently we don't use the permission of AWS connector configured in the S3 cache/restore step instead we use the permissions of stage infrastructure connector

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.

Hi Team- We would like to request support for Test Intelligence in Step Templates. Currently, when attempting to create a Step Template from a working Test Intelligence step in a CI pipeline, we receive validation errors such as: body: is missing but it is required pipelineStatus: is missing but it is required -failureStrategies: is missing but it is required -when: object found, string expected -infrastructure: is missing but it is required

We have a CI pipeline triggered by GitHub Pull Request webhook events that runs functional tests for 14 connectors. We need <+trigger.changedFiles> to be populated at pipeline runtime to conditionally run GitClone steps and functional tests only for connectors whose source files were changed in the PR. Currently, <+trigger.changedFiles> resolves to null at pipeline execution time for PR-based triggers, even though the trigger fires correctly and changedFiles works as a gate condition. Support confirmed this expression is only supported for push-based triggers under the PIPE_TRIGGER_CHANGED_FILES_EXPRESSION flag. We'd like this expression to be extended to PR-based webhook triggers as well, consistent with how it already works for push events. Without this, we're forced to either run the full test suite on every PR across all 14 connectors (wasteful and slow), or maintain a fragile custom script workaround. PR-based triggers are a very common CI pattern, and native support for <+trigger.changedFiles> in this context would benefit a wide range of Harness users.

Currently Harness Service Account User is enable with PAT token. We have instances where business wants to use this Harness Service Account user to have SSH Authentication to clone the Harness Git repos from respective Infrastructure servers to execute Ansible playbooks.

In CI module currently if we add an env variable and value is assigned as some expression which points to the identifier for a secret, the expression does not resolve with the value of the secret. This enhancement is to allow for this functionality as it is possible to do so in CD steps or custom stages such usage is possible.

CI Infrastructure setting enabled for account level. account level enforce to use company wide setting with service account. so that user level not required any own infra build run

Support for Docker Build Secets is through pipeline YAML only. When working with the UI, at the same time, we found our changes getting removed. It would be nice if the UI supported Docker Build Secrets natively

At this time, when Harness cloud credit usage is running low, there is little support for granular notifications of credits hitting thresholds where customers would like to be notified. An example metric that could be tracked and notified would be the "Month-to-date Credit Usage". This would help with transparency around Harness platform utilization and enable proactive conversations about cloud credit usage and allocaiton.