Feature Requests

We need some sort of alerting outside of Harness when an autostopping rule fails to restart an instance as scheduled. Harness shows logs when an instance fails to restart, but we need an alert to bring attention to it

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.

IACM workspace variables are very useful, but it can be hard to track and trace their definitions. Currently, they do not adhere to the variable organization "language" Harness has in place and established for their pipelines. We'd like to see IACM variables as a part of that summary in Pipelines so that it's easier to trace back and see information.

Monitored Service integration with Dynatrace Grail. Grail is a logging solution.

As of today, the drone-git support is available upto windows server 2022 and we are in a need to build the windows based docker image for 2025 hence we are requesting to support drone-git for windows server 2025.

In an STO pipeline with multiple stages, if any stage fails, the vulnerabilities tab does not display the scan results when the pipeline is re-run—even though the results were available in the original run. Please update this behavior so that the results are also shown on the rerun.

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