Feature Requests

When setting up notification for pipeline it should have option to customization such as adding detailed information to the notification body, author needs to tag on message etc.. For example, n the event of a failure, you can tag the PR author, customize the message body, and post to the Teams channel.

Block ability to run container with privilege escalation and user 0 at an account level.

Hi, need help enabling this feature in my project. Enable Matrix Labels By Name, I need this in project CVU. https://app.harness.io/ng/account/H6rHO8vtQYKelD_wgjnMpA/module/ci/orgs/N4C/projects/CVU/settings/default-settings As per support team in United, looks like this needs a feature flag to be enable it to work. thanks for support

Currently Harness does NOT provide support for getting the current date-time stamp, as a variable to use in a pipeline. The current workaround is to use a shell script to get the time and set such a variable which adds delay to the pipeline. It would be more efficient if Harness including a current-date-time variable.

The viewer is not showing enough information to be useful. There are plenty of screen spaces on this view. For example, add the name of the trigger and input-set name causing the execution such that we can at a glance see what was executed and be able to locate all execution by trigger / input-set name. Additionally, show the same trigger name or input set name in the pipeline execution detail view.

Currently, if you have common utility code in your OPA policy, you have to copy and paste it across all of your policy documents to use it. This is not DRY and can potentially lead to lots of unfortunate failures in policy enforcement if this code is updated frequently / in lots of different places and something is missed. It would be nice if common policy code could be stored in a library and imported into the main policy documents.

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.