Feature Requests

When external secret manager token is rotated , we need to reset the perpetual task for the triggers.

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 require the ability to send custom commands, specifically kubectl commands, to the respective Kubernetes clusters. This feature would enable us to manage and interact with our Kubernetes environments more directly and flexibly.

Requesting same notify features for Slack, but for Microsoft Teams. https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/slack-notify-step/

Currently the Harness MCP server runs on stdio locally with API tokens, this is not very enterprise friendly. We need the server to run remotely using http-streamable and use OAUTH authentication.

https://developer.harness.io/docs/platform/delegates/manage-delegates/configure-delegate-proxy-settings/#kubernetes-delegate-proxy-settings Based of this above document only user name and password auth is enabled for proxy. JPMC would like to have Kerberos Auth enabled.

CD containerized group step only supports kubernetes. The request would be to have this orchestrated on a VMs

We need the ability to set ephemeral storage limits on Kubernetes infrastructure for builds, stepGroups with infra, and container steps. Some tasks will use local ephemeral storage for scratch files and other temporary files. If the pods are scheduled on a node that has insufficient disk space for those files, the pod will be evicted which can be very disruptive depending on the process. The ability to set an ephemeral storage request (see Kubernetes docs here) will prevent pods from being scheduled on nodes that have insufficient disk space for the task. It will also prevent tasks that have the ephemeral storage request from being evicted first when disk pressure happens on the node.

We have done STO Sonar integration for our dotnet services and it has been working fine. We are trying to do the same for our windows services, but I'm getting the below error in the Initialize step, 'Back-off pulling image " gcr.io/gcr-prod/harness/sto-plugin:latest "' As suggested in the ticket ( https://support.harness.io/hc/en-us/requests/63663 ), I'm applying Ingestion method for the Sonar and Veracode STO evaluations. https://app.harness.io/ng/account/H6rHO8vtQYKelD_wgjnMpA/all/orgs/AODevSecOps/projects/SandBox/pipelines/POCWindows2/executions/QiCniWtjS5WGL9vP_xAvJA/pipeline?storeType=INLINE Later, we came to know that STO ingestion with Windows OS is only supported when you run the build on Harness cloud. But we are running on our own k8s cluster. Hence I'm submitting this feature request to get the STO support for windows. Regards, Janish

It would be good if in addition to service principles and Managed Identity, Harness support Entra ID workload identity for connecting to Azure from delegates. This would allow service principle type authentication, so scoped to specific org/project, but without the need to manage password. https://learn.microsoft.com/en-us/entra/workload-id/workload-identities-overview