Feature Requests

Expand ability that is there for AWS which allows you to use an AWS connector to have Terraform Plan and Apply Steps assume the role to perform infrastructure provisioning. Would like to have this support GCP, specifically OIDC for us https://developer.harness.io/docs/continuous-delivery/cd-infrastructure/terraform-infra/run-a-terraform-plan-with-the-terraform-apply-step/#aws-connector-provider-credential-authentication-for-terraform-plan-and-apply-steps

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

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

Request to provide the ability/feature to submit a "dry-run" flag to harness API when creating account level templates, as a means of earlier validation.

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.

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

As the title states, the "subset" field needs to be added because it plays a crucial role in the relationship between Istio VirtualService and DestinationRule.

For some reason it seems like deployment type templates are not supported by the move to git operation. Support suggested we get an enhancement request open to get this supported. Technically there's ways to do this by modifying the YAML directly, but we would like this supported natively.