Feature Requests

I've tested this out and I see pod logs now in the Harness GitOps pane. The user experience could see some improvements though. When viewing pod logs in ArgoCD there's a few options that I don't see available in Harness yet. Ability to download logs, and tail on/off toggle. It appears with harness, tail is always enabled, and you have to continuously scroll down on the page to stay caught up.

please enable ff CDS_MARK_PIPELINE_AS_FAILURE

With an AWS connector set as assume role on delegate, the role has by default a timeout of 15 mins. There is a need to increase this timeout from the default of 15 min to a larger amount, say 1 hr. This is supported using an awscli command, where the duration for assume role session can be defined. Same ability to define this in the connector for assume role on delegate is needed.

Currently, only fixed values are supported as allowed values of a runtime input. The idea is to populate a list of values in one step that could be used in the later step as the execution runtime input allowed values. Then, the end user could have the option to choose those allowed values that populated from the previous step as part of the execution runtime input.

Currently the Account Template page does not show if a Template is referenced by any pipelines. This means to determine if a Template is in use or referenced, we have to drill into each individual template to view. Having the ability to view this at the list level, as well as the ability to filter by this, would be a massive time saver.

Cron triggers run off of UTC, with no support for local time (and therefore no support for DST). In locations which use DST, this results in the local time of a job's execution shifting twice per year without manual intervention

It would be nice if we had an option for stage grouping similar to step groups. The thought is if a pipeline has selective stages enabled when i click run, I could check a group of stages to run vs having to select a ton of check boxes

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 request support for the Vault OIDC connector in IaCM workspaces in Harness. Currently, the Vault connector cannot be used within IaCM, limiting secure and centralized secrets management.

While executing the pipeline, how to hide the code/script being displayed in the execution logs.