Feature Requests

Currently either from Execution History or over of a specific service, we can only look through deployments for specific Environments. We would like to see the infrastructures in there. We have multiple infras in each environment and it would be really helpful to see this information without having to dig through each execution.

We would like to propose an enhancement - the ability to scan the shell scripts used in the deployment steps for potentially destructive or risky commands such as rm, mv etc., This feature would help to analyze the scripts prior to execution, ideally during the approval step, and raise alert or warnings if such commands are detected. This allows teams to proactively assess potential impacts before approving a deployment, adding an extra layer of safety and visibility.

Currently the expression suggestion does not show up in the email body. However, the expression resolution works fine and the YAML view still provides the suggestion when the body content is edited. Providing the suggestions for email body shall provide better user experience.

FIS global has requested to support user group in E-Mail Step. This will help them to provide the user group for sending E-mails instead of manually adding all the users.

We are going to be looking at implementing PKCE as a requirement with our organization, and wanted to know if Harness SSO support PKCE with OIDC. It doesn't look like it does from the documentation. We would like Harness to consider supporting this in the future.

Currently when we do ssh/winrm deployments using harness, For each step a new SSH session is created, this new ssh session for each step could lead to login limit set on the SSH server. Therefore, We want a single session to be used for the entire stage of a SSH/Winrm deployment. Please add support for it. Thank you.

Allow looping strategies like matrix, repeat and parallel when invoking a child pipeline as a stage inside a parent pipeline.

Charter Communications has reported recently that in the current UI behavior for single-option selectable dropdowns in pipeline inputs, the selected value does not always display the full text. Additionally, when reopening the dropdown, it is difficult to identify which option was previously selected. A workaround was found by switching the dropdown to a multi-select configuration, where selected values are displayed more clearly. However, this is not a viable long-term solution, as the pipeline logic expects only one value, and allowing multiple selections can lead to errors. Request: We request an enhancement to improve the UI experience for single-select dropdowns by: Ensuring the full selected value text is always visible in the field. Clearly indicating the previously selected option when reopening the dropdown menu. This will significantly improve usability and reduce the chance of configuration errors.

In pipeline triggers, inputYaml parameter is actually a string so the order of elements there matters (service stanza above environment stanza produces different string if those two things were reversed). This a request to document the order of elements expected in that string. Alternatively, treat this as a yaml object where order does not matter. In that case terraform harness provider needs to be adjusted so that it does not produce a diff.

Hi Team, Currently we see Harness audit logs are getting streamed at regular interval (30 mins as mentioned in harness doc). Is there a way we can make it real-time rather than 30 mins interval!? Harness Documentation reference: https://developer.harness.io/docs/platform/governance/audit-trail/audit-streaming/#activate-or-deactivate-streaming