> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/new-to-continuous-delivery/cd-integrations.md). # What's Supported This topic lists the supported CD features and integrations you can use in Harness for deploying and verifying your apps. For a comprehensive list that includes all Harness modules, go to [Supported platforms and technologies](/harness-ai/new-to-harness-platform/platform-whats-supported.md). {% tabs %} {% tab title="Deployments" %}
Platform features for all deployment types
Kubernetes * **Overview:** * [Kubernetes](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/kubernetes-deployments-overview.md) * [Helm charts](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/helm/helm-cd-quickstart.md) (v3) * [Kustomize](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kustomize/kustomize-quickstart.md) * Local ([Harness Community Edition](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/community-ed/harness-community-edition-overview.md)) * **Supported connectors for deployment:** * Kubernetes connector * Username and password * Client key and secret * OIDC authentication * Kubernetes service account * Assume role binding on delegate configuration * Google Cloud connector (GKE authentication) * Service Account * Google Cloud Role on Delegate * Workload Identity * Azure Cloud Connector (AKS Authentication) * Subscription Id * Principal and Service Account * GovCloud Support * [OIDC Authentication](/harness-ai/use-harness-platform/connectors/cloud-providers/add-a-microsoft-azure-connector.md#oidc-authentication) * AWS Cloud Connector (EKS Authentication) * IRSA * Access Key and Secret Key * IAM Role * GovCloud Support * **Supported platforms for deployment:** * Self Hosted Kubernetes * Google Kubernetes Engine * Azure Kubernetes Engine * AWS Elastic Kubernetes Service * Red Hat OpenShift * **Versions and tooling support:** * Kubectl Client Versions: * We support what each of the Cloud Providers support. We recommend users to keep their binary versions up to date. * By default, Harness ships with kubectl client version 1.24.3 * Harness has certified versions: 1.16, 1.25, 1.26, 1.27, 1.28.7, 1.29, 1.30, and 1.31 * You must install the respective client version on the delegate for Harness to leverage it. * Tooling: * OpenShift - oc client binary * Kustomize - kustomize binary * Helm - Helm v3.15.4 (shipped); Helm v3 versions up to v3.21.1 and Helm v4 are supported * **Limitations:** * Helm: * Helm Hooks are not supported for this swimlane. Harness manages and orchestrates the manifests and their release. * There is a known open Helm issue ([helm/helm#10748](https://github.com/helm/helm/issues/10748)) where Helm does not remove a resource on upgrade if another resource with the same `Kind` but a different `apiVersion` exists in the same release. Helm merged a fix but subsequently reverted it due to a regression, and the issue remains unresolved. * Kustomize: * Kustomize Patches are only supported in YAML, not JSON * Kustomize Containerized Plugins are not supported * Kustomize manifests and patches do **not** support the [custom remote manifest](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-kubernetes-category/add-a-custom-remote-script-and-manifests.md) feature. * Harness managed resources: * Deployment * Secrets * ConfigMap * StatefulSet * HorizontalPodAutoScalar * PodDisruptionBudget * **Deployment Performance** * Helm deployments might start failing at the delegate due to a large index.yaml files. This causes a CPU spike on the delegate. If you do not provide enough resources to the delegate, you might see failures in pipeline executions. * Certified Limits: * Index.yaml file size limit 15Mb * 5000 Helm charts have been deployed * Kubernetes delegate size: 8GB, 2 CPU * 10 parallel deployments * **Supported integrations:** * Traffic Shifting for Advanced Deployment Strategies: * Istio * Nginx Ingress Controller * All manifest type sources for fetching Kubernetes resources: * Github * Gitlab * Bitbucket * Custom Remote Source Repository * Harness Local File Store * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) * For Helm Chart Type Manifests we also support: * Generic Git Provider * Google Cloud Storage * Amazon S3 Storage * Helm OCI Repository (ACR, ECR, GAR, Artifactory) * Helm HTTP Server Repository (Nexus, Artifactory) * Artifact repository supported to deploy with manifest: * DockerHub * Amazon Elastic Container Registry * Google Container Registry * Azure Container Registry * Custom Artifact Source * Google Artifact Registry * Github Package Registry * Nexus 3 (Sonatype 3.50.0 and previous supported) * Artifactory For details on what you can deploy, go to [What Can I Deploy in Kubernetes?](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-k8s-ref/what-can-i-deploy-in-kubernetes.md). #### Kubernetes version support The following versions are tested and supported for Kubernetes Canary, Rolling, and Blue/Green deployments: * 1.13.0 * 1.14.0 * 1.15.0 * 1.16.0 * 1.17.0 * 1.18.0 * 1.19.4 * 1.20.0 * 1.21.0 * 1.22.0 * 1.23.0 * 1.24.3 * 1.24.9 * 1.25.6 * 1.26.0 * 1.27.0 * 1.30.10 * 1.31.8 * 1.33.4 * 1.34.0 Go to [Delegate-required SDKs](/harness-ai/use-harness-platform/delegates/delegate/delegate-reference/delegate-required-sdks.md) to view other tools and versions included in Harness. Guidelines: * Harness will officially support 3 previous versions from the last stable release. For example, the current most recent stable release is 1.25.6, and so Harness supports 1.24, 1.23, and 1.22. * Harness supports any other versions of Kubernetes you are using on a best effort basis. * Harness commits to support new minor versions within 3 months of the first stable release. For example, if the stable release of 1.25.6 occurs on April 15th, we will support it for compatibility by July 15th. **Kubernetes Java client compatibility** Harness uses the Kubernetes Java client (`io.kubernetes:client-java`) version **22.0.1**, which is generated from the Kubernetes **1.31** OpenAPI specification. This client is compatible with Kubernetes API servers across multiple versions due to Kubernetes API backward and forward compatibility guarantees. {% hint style="warning" %} **KUBERNETES 1.33 APPROACHING END OF LIFE** Kubernetes 1.33 is approaching end of life (EOL) in July 2026. Harness supports Kubernetes 1.34 to ensure customers can upgrade before 1.33 reaches EOL. A future upgrade to Kubernetes Java client 25.x is planned to provide full support for Kubernetes 1.34 and newer versions. {% endhint %} **Compatibility matrix:** | Kubernetes API Server Version | Harness Client Support Status | Notes | | ----------------------------- | ----------------------------- | --------------------------------------------------------------------------------------------------------- | | 1.13 - 1.31 | Fully Supported | All features tested and certified | | 1.32 - 1.34 | Partially Supported | Deployments work; manifests using fields added after 1.31 cause validation errors (see limitations below) | | 1.35 and later | Partially Supported | Deployments work; manifests using fields added after 1.31 cause validation errors (see limitations below) | **Important notes:** When deploying to Kubernetes clusters running versions 1.32 and above, be aware of the following limitations: * **New API fields:** Kubernetes versions after 1.31 introduce new optional fields in core resource types (Pod, Deployment, DaemonSet, StatefulSet, Job, CronJob). * **Validation behavior:** If your manifests contain fields that were added in Kubernetes versions 1.32 and later, Harness will throw a `KubernetesYamlException` during manifest validation. * **Affected fields:** The following fields added between Kubernetes 1.31 and 1.35 are not recognized by the current client: * `spec.hostnameOverride`, `spec.resources`, `spec.workloadRef` (in PodSpec) * `containers[].restartPolicyRules` (in Container and EphemeralContainer) * `containers[].lifecycle.stopSignal` (in Lifecycle) * `spec.securityContext.seLinuxChangePolicy` (in PodSecurityContext) * `spec.volumes[].projected.sources[].podCertificate` (in VolumeProjection) * `containers[].env[].valueFrom.fileKeyRef` (in EnvVarSource) **Workaround:** If you encounter validation errors when using these newer fields, you have two options: 1. **Remove the new fields:** Remove any Kubernetes 1.32+ fields from your manifests. These fields are optional additions and your deployments will work without them on supported Kubernetes versions. 2. **Use kubectl apply:** Use the Harness **Apply** step instead of the standard deployment steps. The Apply step uses kubectl directly and bypasses the Java client validation, allowing newer fields to pass through to your cluster. #### Helm notes Helm chart dependencies are not supported in Git source repositories. Helm chart dependencies are supported in Helm Chart Repositories. #### Azure AKS clusters To use an AKS cluster for deployment, the AKS cluster parameter `disableLocalAccounts` can be set either `true` or `false`.
Native Helm * **Overview:** * [Native Helm](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/helm/native-helm-quickstart.md) * **Supported connectors for deployment:** * Kubernetes Connector * Username + Password * Client Key and Secret * OIDC Authentication * Kubernetes Service Account * Assume Rolebinding on Delegate Configuration * Google Cloud Connector (GKE Authentication) * Service Account * Google Cloud Role on Delegate * Workload Identity * Azure Cloud Connector (AKS Authentication) * Subscription ID * Principal and Service Account * GovCloud Support * [OIDC Authentication](/harness-ai/use-harness-platform/connectors/cloud-providers/add-a-microsoft-azure-connector.md#oidc-authentication) * AWS Cloud Connector (EKS Authentication) * IRSA * Access Key and Secret Key * IAM Role * GovCloud Support * **Supported platforms for deployment:** * Self Hosted Kubernetes * Google Kubernetes Engine * Azure Kubernetes Engine * AWS Elastic Kubernetes Service * Red Hat OpenShift * **Versions and tooling support:** * Helm Client Versions: Harness ships Helm v3.15.4; Helm v3 versions up to v3.21.1 and Helm v4 are supported * We support what each of the Cloud Providers support, we recommend users to keep their binary versions up to date * Tooling: * OpenShift - oc client binary * Kustomize - kustomize binary * Helm - Helm v3.15.4 (shipped); Helm v4 is also supported * **Limitations:** * Helm v2 is deprecated and not recommended for new deployments. Helm v3 and v4 are supported. * Helm 3 is the default for Harness Helm Chart Deployments. * Helm Plugins are not supported * Only Basic Deployment Strategy supported (No Canary or Blue-Green Support Out of the box) * **Supported integrations:** * Manifest Sources for fetching Helm Chart: * Github * Gitlab * Bitbucket * Generic Git Provider * Custom Remote Source Repository * Google Cloud Storage * Amazon S3 Storage * Helm OCI Repository (ACR, ECR, GAR, Artifactory) * Helm HTTP Server Repository (Nexus, Artifactory) * Harness Local File Store * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) * Artifact Repository for Container Images to deploy with Chart: * DockerHub * Amazon Elastic Container Registry * Google Container Registry * Azure Container Registry * Custom Artifact Source * Google Artifact Registry * Github Package Registry * Nexus 3 (Sonatype 3.50.0 and previous supported) * Artifactory #### Notes Helm chart dependencies are not supported in Git source repositories. Helm chart dependencies are supported in Helm Chart Repositories.
Amazon ECS * **Overview:** * [AWS ECS](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/aws/ecs/ecs-deployment-tutorial.md) * **Supported connectors for deployment:** * AWS Cloud Connector * IRSA * Access Key and Secret Key * IAM Role * GovCloud Support * **Supported platforms for deployment:** * AWS Cloud, any region * AWS - Launch Types: * Amazon ECS - EC2 - Generally Provisioned Instances * Amazon ECS - EC2 - Spot Backed Instances * Amazon ECS - Fargate * **Versions and tooling support:** * AWS SDK * **Supported integrations:** * ECS Service Discovery - Supported via Service Definition * ECS Circuit Breaker - Supported via Service Definition * Artifact Repository: * DockerHub * Amazon Elastic Container Registry * Azure Container Registry * Custom Artifact Source * Github Package Registry * Nexus 3 (Sonatype 3.50.0 and previous supported) * Artifactory * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing ECS manifest.
Amazon AMI/ASG * **Overview:** * [AWS AMI/ASG](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/aws/asg/asg-tutorial.md) * **Supported connectors for deployment:** * AWS cloud connector * IRSA * Access Key and Secret Key * IAM Role * GovCloud Support * **Supported platforms for deployment:** * AWS cloud, any region * **Versions and tooling support:** * AWS SDK * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing your configuration files, User Data, Scaling Policy script and Config File.
AWS Lambda * **Overview:** * [AWS Lambda](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/aws/aws-lambda-deployments.md) * **Supported connectors for deployment:** * AWS Cloud Connector * IRSA * Access Key and Secret Key * IAM Role * GovCloud supported * **Supported platforms for deployment:** * AWS cloud, any region * **Versions and tooling support:** * AWS SDK * **Supported integrations:** * Artifact Repository Supported to Deploy with Function Definition: * Amazon Elastic Container Registry * Amazon S3 * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing AWS Lambda Config File, Lambda Function Definition and Lambda Function Alias Definition.
AWS SAM * **Overview:** * [AWS SAM](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/aws/aws-sam-deployments.md) * **Supported connectors for deployment:** * AWS cloud connector * Access key and secret key * **Supported platforms for deployment:** * AWS cloud, any region * **Versions and tooling support:** * AWS SDK * Harness supports standard SAM templates. * **Supported integrations:** * All Git providers are supported for SAM templates. * Currently, you cannot add artifacts to your Harness SAM service. * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is supported for storing your Values YAML file for manifest type **Values YAML**. * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing AWS SAM manifest when you select manifest type as **AWS SAM Directory**.
Traditional: WinRM * **Overview:** * [WinRM](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/traditional/win-rm-tutorial.md) * **Supported connectors for deployment:** * AWS Cloud Connector * IRSA * Access Key and Secret Key * IAM Role * GovCloud Support * Azure Cloud Connector (AKS Authentication) * Subscription Id * Principal and Service Account * GovCloud Support * **Supported platforms for deployment:** * AWS Cloud * Azure Cloud * Physical Datacenter
Traditional: SSH * **Overview:** * [SSH](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/traditional/ssh-ng.md) * **Supported connectors for deployment:** * AWS Cloud Connector * IRSA * Access Key and Secret Key * IAM Role * GovCloud Support * Azure Cloud Connector (AKS Authentication) * Subscription Id * Principal and Service Account * GovCloud Support * **Supported platforms for deployment:** * AWS Cloud * Azure Cloud * Physical Datacenter * Linux SSH Setups * Ubuntu Version 22+ * RHEL9 (Red Hat Enterprise Linux 9) * SSH libraries supported: * SSHJ: used in our HashiCorp Vault SSH integrations. * JSCH: used in our SSH deployment types. * To see the hostkey formats for these libraries, go to the [SSH implementation comparison](https://ssh-comparison.quendi.de/comparison/hostkey.html). * **Limitations:** * Google Compute Engine (Virtual Machine Targets) * Limited Support, Harness can connect to Google VMs via an SSH Key, not via Google Cloud Authentication
Tanzu Application Service (formerly Pivotal Cloud Foundry) * **Overview:** * [Tanzu Application Services](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/tanzu/tanzu-app-services-quickstart.md) * **Supported connectors for deployment:** * Tanzu Connector * Endpoint URL, Username and Password * **Supported platforms for deployment:** * On Premise Cloud Foundry Installations * VMware Tanzu Platform * **Versions and tooling support:** * Binary Versions: * CF CLI v7 * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing for all TAS manifest type.
Google Functions * **Overview:** * [Google Cloud Functions](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/google-cloud-functions/google-functions.md) * **Supported connectors for deployment:** * Google Cloud Connector * Service Account * **Supported platforms for deployment:** * Google Cloud, any region * **Versions and tooling support:** * Google SDK. Supported versions: * Google Functions Gen 1 * Google Functions Gen 2 * **Deployment strategies:** * Google Functions Gen 1: Basic. * Google Functions Gen 2: Basic, blue green, canary. * **Supported integrations:** * Artifact Repository: * Google Cloud Storage * Google Cloud Storage and Google Cloud Source (Gen 1 Only)
Google Cloud Run * **Overview:** * [Google Cloud Run](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/google-cloud-functions/google-cloud-run.md) * **Supported connectors for deployment:** * Google Cloud Connector * Service Account * Google Cloud Role on Delegate * Workload Identity * OIDC authentication support * **Supported platforms for deployment:** * Google Cloud, any region * **Versions and tooling support:** * Google SDK * gcloud CLI * **Deployment strategies:** * Cloud Run Services: Basic and Canary * Cloud Run Jobs: Task-based execution * **Supported integrations:** * Artifact Repository: * Google Artifact Registry (GAR) * Docker Registry * Container images for deployment: * [harness/google-cloud-run-plugin:1.0.4-linux-amd64](https://hub.docker.com/r/harness/google-cloud-run-plugin/tags) * **Supported workload types:** * Google Cloud Run Services (stateless containerized applications with auto-scaling) * Google Cloud Run Jobs (task-based execution, batch processing, scheduled tasks) * **Limitations:** * Requires containerized execution environment for Cloud Run Jobs
Google Managed Instance Groups (MIG) * **Overview:** * [Google Managed Instance Groups](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/google-cloud-functions/mig.md) * **Supported connectors for deployment:** * Google Cloud Connector * Service Account * OIDC authentication support * **Supported platforms for deployment:** * Google Cloud, any region * **Versions and tooling support:** * Google Compute Engine API * Cloud Service Mesh (HTTPRoute, GRPCRoute) * **Deployment strategies:** * Blue-Green deployment with Cloud Service Mesh traffic management * Basic deployment (Blank Canvas) * **Supported integrations:** * Artifact Repository: * Google Artifact Registry (GAR) * Docker Registry * Container images for deployment: * [harness/google-mig-deploy:0.0.1-linux-amd64](https://hub.docker.com/r/harness/google-mig-deploy/tags) * [harness/google-mig-bluegreen-deploy:0.0.1-linux-amd64](https://hub.docker.com/r/harness/google-mig-bluegreen-deploy/tags) * [harness/google-mig-steady-state:0.0.1-linux-amd64](https://hub.docker.com/r/harness/google-mig-steady-state/tags) * [harness/google-mig-traffic-shift:0.0.1-linux-amd64](https://hub.docker.com/r/harness/google-mig-traffic-shift/tags) * [harness/google-mig-bluegreen-rollback:0.0.1-linux-amd64](https://hub.docker.com/r/harness/google-mig-bluegreen-rollback/tags) * [harness/gce-provision-backend-service:0.0.1-linux-amd64](https://hub.docker.com/r/harness/gce-provision-backend-service/tags) * **Supported workload types:** * Regional MIGs (multi-zone distribution for high availability) * Zonal MIGs (single-zone deployment) * **Limitations:** * Requires containerized execution environment (Container Step Group)
Spot Instances * **Overview:** * [Spot Elastigroup deployments](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/aws/spot/spot-deployment.md) * **Supported connectors for deployment:** * Spot Connector * AccountID + API Token * **Supported platforms for deployment:** * AWS cloud, any region * **Limitations:** * Deployment Behavior: * Incremental Traffic Shifting for SpotInst Deployment is not supported * VM-based Deployments are supported via Elastigroup configuration
Serverless.com Framework * **Overview:** * [Serverless.com Framework](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/serverless/serverless-lambda-cd-quickstart.md) (AWS Lambda) * **Supported connectors for deployment:** * AWS Cloud Connector * IRSA * Access Key and Secret Key * IAM Role * **Supported platforms for deployment:** * AWS cloud, any region * **Versions and tooling support:** * Supported Binary Versions: * serverless.com 2.x * serverless.com 3.x * serverless.com 4.x * serverless.com 1.x (deprecated - limited support, not all capabilities supported) * **Limitations:** * Deployment Behavior: * Harness only supports AWS Lambda Functions to be deployed via Serverless.com Framework * Harness builds and deploys Lambda Functions. You cannot split up the tasks to build functions and deploy functions separately as part of Harness support. * Not supported application types: * Google Functions * Azure Functions * Basic deployment supported. No out-of-the-box canary and blue green deployment supported. * **Supported integrations:** * Serverless.com plugins: * Harness supports all the Serverless.com plugins. Please make sure they are compatible with the version of Serverless.com you are using. * Artifact Repository: * DockerHub * Amazon Elastic Container Registry * Artifactory * Amazon S3 * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is supported for storing your Values YAML file for manifest type **Values YAML**. * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing Serverless Lambda Manifest when you select manifest type as **Serverless Lambda Manifest** as well as for storing Config File.
Azure WebApps * **Overview:** * [Azure Web Apps](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/azure/azure-web-apps-tutorial.md) * **Supported connectors for deployment:** * Azure Cloud Connector (AKS Authentication) * Subscription Id * Principal and Service Account * GovCloud Support * [OIDC Authentication](/harness-ai/use-harness-platform/connectors/cloud-providers/add-a-microsoft-azure-connector.md#oidc-authentication) * **Supported platforms for deployment:** * Azure cloud, any Region * **Versions and tooling support:** * Azure SDK * **Limitations:** * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing your Application Settings Script File in Azure Webpps.
Azure Functions * **Overview:** * [Azure Functions](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/azure/azure-function-tutorial.md) * **Supported connectors for deployment:** * Azure Cloud Connector * Subscription Id * Principal and Service Account * GovCloud Support * [OIDC Authentication](/harness-ai/use-harness-platform/connectors/cloud-providers/add-a-microsoft-azure-connector.md#oidc-authentication) * **Supported platforms for deployment:** * Azure cloud, any Region * **Versions and tooling support:** * Azure SDK * Azure Functions Runtime * **Deployment strategies:** * Basic deployment * **Supported integrations:** * Artifact Repository: * Docker Hub * Amazon Elastic Container Registry (ECR) * Google Artifact Registry (GAR) * Container images for deployment: * [Docker Image for Azure Function Plugin](https://hub.docker.com/r/harness/azure-function-plugin/tags) * [ECR Image for Azure Function Plugin](https://gallery.ecr.aws/harness/harness/azure-function-plugin) * [GAR Image for Azure Function Plugin (Europe)](https://console.cloud.google.com/artifacts/docker/gar-prod-setup/europe/harness-public/harness%2Fazure-function-plugin) * **Limitations:** * Requires containerized execution environment (Kubernetes cluster) * [Harness Code Repository](https://app.gitbook.com/s/oTP6ysjQCQlt5GlFHRfs/README) is not supported for storing Azure Functions configuration files
Builds in CD Continuous Integration (CI) can be performed in Harness using the module and [CI pipelines](/continuous-integration/new-to-harness-ci/key-concepts.md). If you are using Harness Continuous Delivery (CD) but not Harness Continuous Integration (CI), you can still perform CI using the Jenkins step in your CD stage. Harness integrates with [Jenkins](https://jenkins.io/), enabling you to run Jenkins jobs and dynamically capture inputs and outputs from the jobs. Harness has been tested with the following versions of Jenkins: * 2.432 * 2.424 * 2.425 * 2.401.2 * 2.414.2 * 2.398 * 2.397 * **Overview:** * [Run Jenkins jobs in CD pipelines](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/builds/run-jenkins-jobs-in-cd-pipelines.md)
GitOps * **Overview:** * [GitOps](/continuous-delivery/use-gitops/get-started/harness-git-ops-basics.md) * [GitOps Quickstart](/continuous-delivery/use-gitops/get-started/harness-cd-git-ops-quickstart.md) Harness GitOps lets you perform GitOps deployments in Harness. You define the desired state of the service you want to deploy in your Git manifest, and then use Harness GitOps to sync state with your live Kubernetes cluster. GitOps supports the following: * GitOps reconciler: * **Argo CD only.** Flux is not supported. If you run Flux workloads, go to [Migrate from Flux to Argo CD](/continuous-delivery/use-gitops/get-started/migrate-flux-to-argo.md) to move them to Argo CD. * Argo CD versions supported: * 2.8.2 * 3.1.8 (Bundled with Helm 3.18.4 and Kustomize 5.7.0) * Source Repositories: * All Git providers. * HTTP Helm repos. * Target clusters: * Kubernetes clusters hosted on any platform: * GKE. * AKS. * EKS. * Other Kubernetes-compliant clusters. * OpenShift version 3.11, 4.x. * Minikube. * Kubernetes Operations (kops). * Repository Certificates: * TLS Certificate (PEM format). * SSH Known Host Entry. * GnuPG Keys: * GnuPG Public Key Data (ASCII-armored). * **Limitations:** * Self-hosted environments * Agents installed in custom namespaces are not yet supported.
Local (Harness Community Edition) Harness CD Community Edition is a lightweight version of Harness that you can download and run on your laptop or any VM. Harness CD Community Edition is intended to get devs started with Harness quickly without having to sign up for a Harness SaaS account. * **Overview:** * [Harness CD Community Edition overview](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/community-ed/harness-community-edition-overview.md) * [Harness Community Edition deployments](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/community-ed/harness-community-edition-quickstart.md)
Custom For non-native deployments, Harness provides a custom deployment option using Deployment Templates. * **Overview:** * [Custom deployments using Deployment Templates](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/custom/custom-deployment-tutorial.md)
{% endtab %} {% tab title="Provisioners" %} Harness supports the following infrastructure provisioning tools: * [Terraform](/continuous-delivery/use-continuous-delivery/provision-infrastructure/terraform-infra/terraform-provisioning-with-harness.md) * [Terragrunt](/continuous-delivery/use-continuous-delivery/provision-infrastructure/terragrunt-howtos.md) * [Azure ARM](/continuous-delivery/use-continuous-delivery/provision-infrastructure/azure-arm-provisioning.md) * [Azure Blueprint](/continuous-delivery/use-continuous-delivery/provision-infrastructure/azure-blueprint-provisioning.md) * [AWS CloudFormation](/continuous-delivery/use-continuous-delivery/provision-infrastructure/cloudformation-infra/cloud-formation-provisioning-with-harness.md) * [Shell script](/continuous-delivery/use-continuous-delivery/provision-infrastructure/shell-script-provisioning.md) (custom) #### Terraform version support Harness does not include Terraform on the Harness Delegate. You must install Terraform on the Delegate when using Terraform in Harness. For more information, go to [Terraform How-tos](/continuous-delivery/use-continuous-delivery/provision-infrastructure/terragrunt-howtos.md). Harness supports the following Terraform versions: * v1.3.5 * v1.1.9 * v1.0.0 * v0.15.5 * v0.15.0 * v0.14.0 Here's an example install script for the Harness Delegate: ```bash # Install TF microdnf install unzip curl -O -L https://releases.hashicorp.com/terraform/1.3.5/terraform_1.3.5_darwin_amd64.zip unzip terraform_1.3.5_darwin_amd64.zip mv ./terraform /usr/bin/ # Check TF install terraform --version ``` Some Harness features might require specific Terraform versions. {% hint style="info" %} **NOTE** Harness also supports Terraform Cloud and Enterprise. {% endhint %} {% endtab %} {% tab title="Controls/Utilities" %} * **Containerized steps:** * [Containerize step groups](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/containerized-steps/containerized-step-groups.md) * Multiple step types can be run containerized. * **Controls:** * [Strategies](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-concepts.md): basic, rolling, canary, blue green, custom. * [Barriers](/continuous-delivery/use-continuous-delivery/manage-deployments/synchronize-deployments-using-barriers.md) * [Resource Constraints](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-resource-constraints.md) * [Queue steps](/continuous-delivery/use-continuous-delivery/manage-deployments/control-resource-usage-with-queue-steps.md) * [Deployment freeze](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-freeze.md) * [Failure strategies](/harness-ai/use-harness-platform/pipelines/failure-handling/define-a-failure-strategy-on-stages-and-steps.md) * [Conditional executions](/harness-ai/use-harness-platform/pipelines/step-skip-condition-settings.md) * [Looping strategies](/harness-ai/use-harness-platform/pipelines/looping-strategies/looping-strategies-matrix-repeat-and-parallelism.md) * [Triggers](https://app.gitbook.com/s/3F2TpHXhur2QtQnORSM9/use-harness-platform/triggers/README) * [Input set and overlays](/harness-ai/use-harness-platform/pipelines/input-sets.md) * **Utilities:** * [Run a Docker container in a CD stage](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/container-step.md) * [Using HTTP requests in CD pipelines](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/http-step.md) * [Using shell scripts in CD stages](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/shell-script-step.md) * [Use the Command step to download or copy artifacts and configs, or run scripts](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/download-and-copy-artifacts-using-the-command-step.md) * [Run a step on multiple target instances](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/run-a-script-on-multiple-target-instances.md) * [Wait step](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/wait-step.md) * [Email step](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/email-step.md) * [JSON and XML functors](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/utilities/json-and-xml-functors.md) * **Build:** * [Background step](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/containerized-steps/background-step.md) * [Git Clone step](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/containerized-steps/git-clone-step.md) * [Run step](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/containerized-steps/run-step.md) * [Plugin step](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/containerized-steps/plugin-step.md) {% endtab %} {% tab title="File Store" %} Manifests, specifications, config files, and other deployment files can be pulled from the following providers: * [Harness File Store](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/add-inline-manifests-using-file-store.md) * [Git on any platform](/harness-ai/use-harness-platform/connectors/code-repositories/ref-source-repo-provider/git-connector-settings-reference.md) * [Github](/harness-ai/use-harness-platform/connectors/code-repositories/ref-source-repo-provider/git-hub-connector-settings-reference.md) * [GitLab](/harness-ai/use-harness-platform/connectors/code-repositories/ref-source-repo-provider/git-lab-connector-settings-reference.md) * [Bitbucket](/harness-ai/use-harness-platform/connectors/code-repositories/ref-source-repo-provider/bitbucket-connector-settings-reference.md) * [AWS CodeCommit](/harness-ai/use-harness-platform/connectors/cloud-providers/ref-cloud-providers/aws-connector-settings-reference.md) * [Azure Repos](/harness-ai/use-harness-platform/connectors/code-repositories/connect-to-a-azure-repo.md) The following table lists where you can store your manifests or config files for each integration. | | **Github** | **Gitlab** | **Bitbucket** | **Harness File Store** | **Any Git** | **OCI Helm** | **HTTP Helm** | **AWS S3** | **Custom** | **Google Cloud Storage** | **Inherit from manifest** | | ---------------------------- | ---------- | ---------- | ------------- | ---------------------- | ----------- | ------------ | ------------- | ---------- | ---------- | ------------------------ | ------------------------- | | **Kubernetes** | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | **Values YAML** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | ✅ | | ✅ | | **Kustomize** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | | | | | **Kustomize Patches** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | | | ✅ | | **OpenShift Template** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | ✅ | | | | **OpenShift Params** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | ✅ | | | | **AWS ECS** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | | | ✅ | | **AWS SAM** | ✅ | ✅ | ✅ | ✅ | ✅ | | | ✅ | | | | | **Helm Chart** | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | **Serverless.com Framework** | ✅ | ✅ | ✅ | ✅ | ✅ | | | ✅ | | | | | **SSH** | | | | ✅ | | | | | | | | | **WinRM** | | | | ✅ | | | | | | | | | **Azure Web Apps** | | | | ✅ | | | | | | | | | **Google Cloud Function** | ✅ | ✅ | ✅ | ✅ | ✅ | | | | | | | The following table lists supported manifest overrides for each integration. | **Deployment Type** | **Supported Manifest Overrides** | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Kubernetes | | | Helm | | | AWS ECS | | | AWS ASG | N/A | | AWS Lambda | | | AWS SAM | | | Azure Web Apps | | | Azure Functions | N/A | | Tanzu Application Services | | | SSH | N/A | | WinRM | N/A | | Serverless.com Framework | | | Google Cloud Functions | N/A | | Google Cloud Run | N/A | | Spot Elastigroup | N/A | | {% endtab %} | | {% tab title="Artifacts" %} All artifact sources are covered in [CD artifact sources](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/artifact-sources.md). * Harness Artifact Registry * Docker registry on any platform * Google Container Registry (GCR) * Google Cloud Storage (GCS) * Google Artifact Registry * Amazon Elastic Container Registry (ECR) * AWS S3 * Azure Container Registry (ACR) * Azure DevOps Artifacts * Nexus 2 and Nexus 3 (Sonatype 3.50.0 and previous supported) * Artifactory * Jenkins * Bamboo * Github packages * HTTP Helm * OCI Helm * Custom artifact source Harness uses **Metadata only** when downloading artifact sources. For pulling Docker images from Docker repos, Harness is restricted by the limits of the Docker repo. For example, [Docker Hub limits](https://docs.docker.com/docker-hub/download-rate-limit/). The maximum number of artifact image tags fetched by Harness that is 10000. The following table lists Harness integrations and their artifact source support: | | **Harness Artifact Registry** | **Docker Hub** | **ECR** | **GCR** [Deprecation Notice](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/artifact-sources.md#google-container-registry-gcr) | **GCS** | **ACR** | **Artifactory** | **Nexus 3** | **Custom** | **Google Artifact Registry** | **Github Artifact Registry** | **Jenkins** | **AWS S3** | | ---------------------------- | ----------------------------- | -------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ------- | --------------- | ----------- | ---------- | ---------------------------- | ---------------------------- | ----------- | ---------- | | **Kubernetes** | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | | | **Helm** | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | | | | | | **AWS ECS** | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | | | | | | **AWS ASG** | | | | | | | | | | | | | | | **AWS Lambda** | ✅ | | ✅ | | | | | | | | | | ✅ | | **Azure Web Apps** | ✅ | ✅ | | | | ✅ | ✅ | ✅ | | | | | | | **Azure Functions** | ✅ | ✅ | ✅ | | | | | | | ✅ | | | | | **Tanzu** | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | | | | | | | **SSH** | ✅ | | | | | ✅ | ✅ | ✅ | ✅ | | | ✅ | ✅ | | **WinRM** | ✅ | | | | | | ✅ | ✅ | ✅ | | | ✅ | ✅ | | **Serverless.com Framework** | ✅ | | ✅ | | | | ✅ | | | | | | ✅ | | **Google Cloud Function** | | | | | ✅ | | | | | | | | | | **Google Cloud Run** | | ✅ | | | | | | | | ✅ | | | | | **Google MIG** | | ✅ | | | | | | | | ✅ | | | | | {% endtab %} | | | | | | | | | | | | | | {% tab title="Ticketing/Approvals" %} You can use the following ticketing systems for creating and updating tickets, and as approval gates: * Jira ([ticketing](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/ticketing-systems/create-jira-issues-in-cd-stages.md), [approvals](/harness-ai/use-harness-platform/approvals/adding-jira-approval-stages.md)) * ServiceNow ([ticketing](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/ticketing-systems/create-service-now-tickets-in-cd-stages.md), [approvals](/harness-ai/use-harness-platform/approvals/service-now-approvals.md)) * [Harness manual approvals](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/approvals/using-harness-approval-steps-in-cd-stages.md) #### Approval workflows Harness provides flexible approval workflows that can be integrated into your deployment pipelines: * **Harness Approvals**: Native approval steps that can be configured with user groups, automatic approvals, and custom approval logic * **Jira Approvals**: Integrate with Jira to use existing ticket workflows for deployment approvals * **ServiceNow Approvals**: Leverage ServiceNow change management processes for deployment gates * **Custom Approvals**: Build custom approval logic using conditional execution and API integrations Key capabilities: * User group-based approvals with combined or any-member logic * Auto-reject previous deployments when new ones reach approval stage * Include stage execution details for informed decision-making * Timeout and failure strategy configuration * Approval notifications via email, Slack, MS Teams For detailed documentation, go to [Approvals](https://app.gitbook.com/s/3F2TpHXhur2QtQnORSM9/use-harness-platform/approvals/README). For frequently asked questions about ticketing and approvals in CD, go to [Approvals and Ticketing FAQs](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/approvals/approvals-and-ticketing-faqs.md). **Note:** All detailed approval and ticketing FAQs have been moved to the dedicated [Approvals and Ticketing FAQs](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/approvals/approvals-and-ticketing-faqs.md) page for better organization and easier reference. {% endtab %} {% tab title="Governance" %} Harness Policy As Code uses [Open Policy Agent (OPA)](https://www.openpolicyagent.org/) as the central service to store and enforce policies for the different entities and processes across the Harness platform. You can centrally define and store policies and then select where (which entities) and when (which events) they will be applied. Currently, you can define and store policies directly in the OPA service in Harness. Soon, you will be able to use remote Git or other repos (e.g. OCI-compatible registries) to define and store the policies used in Harness. * [Harness Policy As Code overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/advanced/cd-governance/harness-governance-overview.md) * [Harness Policy As Code quickstart](/continuous-delivery/use-continuous-delivery/cd-building-blocks/advanced/cd-governance/harness-governance-quickstart.md) * [Add a Policy step to a pipeline](/continuous-delivery/use-continuous-delivery/cd-building-blocks/advanced/cd-governance/add-a-governance-policy-step-to-a-pipeline.md) #### Policy as Code limitations * When configuring a policy for testing, users must have a pipeline that has a policy run against it (success or failed) to capture the pipeline's expanded JSON for the policy studio testing terminal. * Policies can only be run against one document (one JSON payload sent for OPA evaluation). You cannot run a policy against multiple documents. * Not all Harness entities are supported with policies: * For CD: service, environment, infrastructure, and overrides are on the roadmap for integration. * For Platform: service account, API key, and token are on the roadmap for policy integration. * For other product modules: entities will be added as needed. * Harness does not support OPA bundles. * Harness does not support data imports from external sources. * Harness does not support `allow`, to support this use case you need to invert the logic, Harness OPA supports deny and not allow. For frequently asked questions about OPA policies and governance, go to [OPA FAQs](/continuous-delivery/use-continuous-delivery/cd-building-blocks/advanced/cd-governance/opa-faqs.md). **Note:** All detailed governance and OPA policy FAQs have been moved to the dedicated [OPA FAQs](/continuous-delivery/use-continuous-delivery/cd-building-blocks/advanced/cd-governance/opa-faqs.md) page for better organization and easier reference. {% endtab %} {% endtabs %} #### Notes * AWS and Azure GovCloud: Harness is now certified in Azure GovCloud and AWS GovCloud. ### Harness Self-Managed Enterprise Edition (SMP) including offline Environments All CD features supported in Harness SaaS are also supported in Self-Managed Enterprise Edition with the following exceptions: * **Dashboards:** Harness [CD Dashboards](https://developer.harness.io/docs/continuous-delivery/monitor-deployments/monitor-cd-deployments) might not be completely functional with a bundled [Timescale community edition](https://docs.timescale.com/about/latest/timescaledb-editions/) version installation. * **Triggers:** The feature flag `CD_GIT_WEBHOOK_POLLING` must be enabled for Github polling with two factor authentication. For more information, go to [Polling frequency](https://developer.harness.io/docs/platform/triggers/triggers-reference/#polling-frequency). * **ServiceNow:** ServiceNow versions [Utah](https://docs.servicenow.com/bundle/utah-release-notes/page/release-notes/family-release-notes.html) and earlier are supported. * **Jira:** Jira on-premise versions < 9.0 are supported. To support Jira on-premise >= 9.0, the feature flag `SPG_USE_NEW_METADATA` must be enabled. * **Policy as Code:** Harness Git Experience support for OPA policies is not supported in Self-Managed Enterprise Edition. * **Harness AI:** To support Harness AI in Self-Managed Enterprise Edition running in an offline environment, you must add `https://harness.openai.azure.com` to your allowlist. ### Deploy pipeline log streaming Harness CD supports streaming deploy pipeline stage execution logs from your self-managed delegate to your own observability backend, such as Grafana Loki, Splunk, Datadog, or Elasticsearch. When enabled, the delegate writes CD execution logs as structured JSON to stdout in parallel with the standard Harness Log Service. A log collector such as OpenTelemetry Collector, Fluent Bit, or Vector then forwards those logs to your backend. Go to [Stream pipeline logs](/harness-ai/use-harness-platform/delegates/delegate/manage-delegates/stream-pipeline-logs-to-observability-backend.md) to set this up. *** ### Active CD Feature flags Some Harness CD features are released behind feature flags to get feedback from specific customers before releasing the features to the general audience. Feature development statuses are categorized as [Beta, GA, or Limited GA](/harness-ai/new-to-harness-platform/overview.md#beta-limited-ga-and-ga-definitions). The following table describes active feature flags relevant to Harness CD. To enable a feature flag in your Harness account, contact [Harness Support](mailto:support@harness.io). | Flag | Description | | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CDS\_GITOPS\_POST\_PROD\_ROLLBACK | Enables post-production rollback for GitOps applications from the Services dashboard. After a successful pipeline deployment, a Rollback button appears in the Services tab allowing you to execute the pipeline's rollback steps. Go to [Post-production rollback from the Services dashboard](/continuous-delivery/use-gitops/application/rollback-gitops-applications.md#post-production-rollback-from-the-services-dashboard) for more information. **This feature is in Beta.** | | OPA\_GITX\_PARITY | Enables enhanced Git Experience UI features for OPA policies. **This feature is in Limited GA.** | | OPA\_GITX\_DIRECT\_FETCH | Enables direct batch fetch of policy content from Git during evaluation, improving performance and error reporting. **This feature is in Limited GA.** | | CDS\_AWS\_DESCRIBE\_REGIONS\_OPTIONAL | When enabled, Harness uses `sts:GetCallerIdentity` instead of `ec2:DescribeRegions` for AWS connector validation, removing the EC2 IAM permission requirement. Requires delegate version `889xx` or later. For details, go to [DescribeRegions and connector validation](/harness-ai/use-harness-platform/connectors/cloud-providers/ref-cloud-providers/aws-connector-settings-reference.md#describeregions-and-connector-validation). **This feature is in Limited GA.** | | CDS\_HELM\_IMPROVED\_SOPS\_SUPPORT\_FOR\_SERVICE\_HOOKS | For **Native Helm**, enables per-task values override directories and service hook variables (`VALUES_OVERRIDE_DIRECTORY`, `OVERRIDE_FILES`) for SOPS and custom overrides. Requires delegate `26.03.88700` or later. See [SOPS and values overrides in Native Helm service hooks](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/helm/native-helm-sops-overrides-service-hooks.md). **This feature is in Limited GA.** | | CDS\_GITX\_WEBHOOK\_SYNC\_ENTITY\_METADATA | Enables automatic metadata sync (name, description, and tags) for [service](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/services-overview.md#metadata-sync-with-bidirectional-sync), [environment, and infrastructure](/continuous-delivery/use-continuous-delivery/cd-building-blocks/environments/environment-overview.md#metadata-sync-with-bidirectional-sync) entities during [bidirectional sync](/harness-ai/use-harness-platform/git-experience/gitexp-bidir-sync-setup.md). When enabled, metadata changes committed to the default branch in Git are automatically propagated to the corresponding entity in Harness. This sync applies only to the default branch; metadata changes on other branches are not synced. **This feature is in Limited GA.** | | OPA\_RUN\_ON\_CUSTOMER\_INFRA | Enables the ability to configure policy sets to [run on your own infrastructure](/harness-ai/use-harness-platform/governance/policy-as-code/run-policies-in-your-environment.md) instead of Harness SaaS. This is useful when policies need secrets or tokens to connect to external systems like ServiceNow, Jira, or internal databases, ensuring your secrets never leave your trust boundary. Available only for policy sets configured for Pipeline entity type with the On Run action. **This feature is in Limited GA.** | | OPA\_INCLUDE\_GROUP\_ROLE\_ASSIGNMENTS | When enabled, OPA policy evaluation includes roles inherited through user groups in `input.metadata.roleAssignmentMetadata` for **USER** principals, not only roles assigned directly to the user. Use this when [OPA policies](/harness-ai/use-harness-platform/governance/policy-as-code/harness-governance-overview.md#policy-input-payload-user-metadata) check `roleAssignmentMetadata` to allow or deny actions based on RBAC roles. When disabled (default), only direct user role assignments are included, so policies may not see group-inherited roles. **This is a behavior change for existing OPA policies. Review policies before enabling.** **This feature is in Limited GA.** | | PIPE\_OPA\_DISABLE\_EVALUATION\_DATA\_IN\_LISTING | When enabled, the policy evaluations list API (`GET /api/v1/evaluations`) no longer returns evaluation payload data inline. The `details` field will be `null` in list responses; full evaluation details remain available via the individual evaluation endpoint (`GET /api/v1/evaluations/{id}`). In the UI, the Policy Sets column in **Governance > Policy Evaluations** shows a **View Details** button instead of inline policy set names. This change is part of memory optimisation efforts to improve service reliability for accounts with large evaluation payloads. **This feature is in Limited GA.** | | PIPE\_FAIL\_USER\_MARKED\_FAIL\_ALL\_INTERRUPT\_WITHOUT\_LEAF\_NODES | When enabled, this flag ensures that interrupting a pipeline execution (for example, marking it as failed or expiring it) correctly stops all running tasks and releases resources, preventing resource locking and potential pipeline stalls. **This is a Beta fix** | | CDS\_CONTAINER\_STEP\_DELEGATE\_SELECTOR\_PRECEDENCE | Enable this feature to honor delegate selector precedence in container steps, including git clone operations. When enabled, delegate selectors defined at the pipeline, step group, or step level will take precedence over connector-level delegate selectors for container-based deployments. **This is a Beta feature.** | | CDS\_ENABLE\_TERRAGRUNT\_V1\_SUPPORT | Enables support for Terragrunt versions 0.78.0 and later, which introduced breaking changes in command formats. When enabled, Harness automatically detects the Terragrunt version and uses the appropriate command format (new `--all` flag instead of `run-all` subcommand, `--non-interactive` instead of `--terragrunt-non-interactive`, and updated workspace command structure). The system falls back to legacy commands for versions below 0.78.0. For more information, refer to the [Terragrunt documentation](/continuous-delivery/use-continuous-delivery/provision-infrastructure/terragrunt-howtos.md#supported-terragrunt-and-terraform-versions). **This feature is in Limited GA.** | | PIPE\_STORE\_TEMPLATE\_REFERENCE\_SUMMARY\_PER\_EXECUTION | Enables users to view the [template version used during pipeline execution](/harness-ai/use-harness-platform/templates/use-a-template.md#template-details-in-execution), helping them identify the exact version label applied at runtime. **This feature is in Limited GA.** | | PIPE\_BARRIERS\_FOR\_CHAINED\_PIPELINES | Enables users to configure [barrier synchronization across parent and child pipelines](/harness-ai/use-harness-platform/pipelines/barriers.md), allowing child pipelines to reference and use barriers defined in parent pipelines via runtime inputs for coordinated deployments. **This feature is in Limited GA.** | | PIPE\_CREATE\_EDIT\_PERMISSION\_SPLIT\_MIGRATION, PIPE\_CREATE\_EDIT\_PERMISSION\_SPLIT | Enables users to configure separate **Create** and **Edit** authorization grants for pipelines and templates, offering more [granular RBAC control](/harness-ai/use-harness-platform/platform-access-control/rbac-in-pipelines-templates-and-secrets.md#split-the-create-and-edit-permissions). Enabling this feature requires a migration of existing resources, which will be guided by Harness Support. **This feature is in Limited GA.** | | PIPE\_PROJECT\_LEVEL\_EXECUTION\_CONCURRENCY, PIPE\_ENABLE\_QUEUE\_BASED\_PLAN\_CREATION | Enables users to configure [**Project-Level Pipeline Execution Concurrency**](/harness-ai/use-harness-platform/pipelines/pipeline-settings.md#project-level-pipeline-execution-concurrency), allowing them to allocate execution capacity across High-Priority and Low-Priority partitions. **This feature is in Limited GA.** | | PIPE\_POPULATE\_REQUIRED\_AND\_DESC\_METADATA\_INTO\_REFERENCING\_ENTITY | Enables users to preserve the **Required** flag and **Description** metadata for Service and Environment variables in Pipelines and Templates, ensuring these attributes are retained when used as runtime inputs. **This feature is in Limited GA** | | PIPE\_GITX\_DISABLE\_SKIP\_GIT\_WEBHOOK\_REGISTRATION | Enables users to register GitX webhooks without creating them in Git providers, allowing webhook setup via an intermediary service without requiring connector-level registration permissions. **This feature is in Limited GA.** | | CDS\_DEPLOY\_SERVICE\_IN\_PARALLEL\_FIX | Enables users to retain the selected chart version when toggling the *Deploy Service in Parallel* option, even when both are configured as runtime inputs. **This feature is in Limited GA**. | | PIPE\_DISABLE\_PIPELINE\_NOTIFICATIONS\_ON\_ROLLBACK | Enables users to suppress independent `PIPELINE_START` and `PIPELINE_SUCCESS` notifications during rollback, ensuring that only the main pipeline's `PIPELINE_FAILED` notification is sent. **This feature is in Limited GA**. | | CDS\_K8S\_NOT\_ADD\_TRAFFIC\_ROUTING\_TO\_CANARY\_WORKLOAD | Enables users to prevent Virtual Services from being deleted during the Canary Delete step in Kubernetes deployments, preserving traffic routing configurations during rollback. **This feature is in Limited GA**. | | CDS\_ASG\_MULTI\_DEPLOY\_ROLLBACK\_SUPPORT | Enables users to [deploy multiple ASGs in a single stage](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/aws/asg/asg-tutorial.md#multi-asg-deployments-and-parallel-rollback-single-serviceenvironmentinfrastructure) for the same service, environment, and infrastructure, with automatic parallel rollback triggered on failure. **This feature is in Limited GA.** | | PIPE\_FAIL\_ALL\_FAILURE\_STRATEGY | Enables users to configure [fail fast behavior](/harness-ai/use-harness-platform/pipelines/failure-handling/fast-fail.md) in parallel executions, where a failure in any step or stage immediately fails the pipeline and triggers the configured failure strategy. **This feature is in Limited GA**. | | PIPE\_ENABLE\_INPUT\_SET\_FILTER | Enables users to view applied [**Input Sets**](/harness-ai/use-harness-platform/pipelines/input-sets.md#view-and-filter-executions-by-input-set) in the Inputs tab as clickable links and see them in the trigger summary on the execution history page. **This feature is in Limited GA**. | | PIPE\_ENABLE\_GITHUB\_ENTERPRISE\_PROVIDER\_FLOW | Enables users to integrate their GitHub Enterprise instance using Harness’s OAuth provider configuration, instead of legacy token-based connectors. Harness's built-in Secret Manager is not supported with this provider flow, you must use a custom Secret Manager accessible to your delegate. **This feature is in Limited GA.** | | PIPE\_SUPPORT\_MULTIPLE\_TIMEZONES\_IN\_CRON\_TRIGGERS | Enables users to select timezones for [Cron triggers](/harness-ai/use-harness-platform/triggers/schedule-pipelines-using-cron-triggers.md) using IANA Time Zone names, providing more control over when pipelines are triggered. **This feature is in Limited GA.** | | PIPE\_EXECUTION\_ID\_FILTER | Enables users to filter pipeline executions by build ID, making it easier to quickly locate specific runs without scrolling through large execution lists. **This feature is in Limited GA.** | | PIPE\_ENABLE\_QUEUED\_BASED\_CUSTOM\_TRIGGERS | Harness now supports custom webhook trigger execution via the **Queue Service**, improving reliability and scalability. This ensures webhook triggers are processed efficiently even under high load, without one customer's activity impacting others. **This feature is in Limited GA.** | | CDS\_ENABLE\_STEADY\_STATE\_CHECK\_WITHOUT\_MANAGED\_WORKLOADS | Enables users to run **Service PreHooks** for Kubernetes **CronJob** workloads during the **Wait for Steady State** phase. Previously, PreHooks did not trigger for CronJobs. This feature ensures PreHooks are executed consistently across workload types. **This feature is in Limited GA.** | | CDS\_OVERRIDES\_DISABLE\_ENV\_API\_UPDATES | Enables users to view environment variable references and YAML overrides more accurately in the UI. Previously, secrets continued to appear as referenced in an environment even after removal. This fix improves clarity in the environment configuration view. **This feature is in Limited GA.** | | CDS\_AWS\_LAMBDA\_ECS\_TAG\_SUPPORT | Users can now **create, update, and delete tags** in **AWS Lambda** and **AWS ECS deployments**, ensuring that all specified tags in the YAML manifest are correctly propagated during the deployment process and accurately reflected in the AWS Console. **This feature is in Limited GA.** | | CDS\_SERVICE\_DASHBOARD\_SIMPLIFICATION | Improves Service Dashboard load time by optimizing API calls and relocating certain data to enhance performance. The service dashboard graph has been moved to the Analytics tab. Users can switch between the **Service** and **Analytics** tabs at the top right of the **Service Dashboard** page. **This feature is in Limited GA.** | | PIPE\_CUSTOM\_NOTIFICATION\_TEMPLATES | Enables customized notifications for all types of Pipeline Notifications and for Webhook-based Centralized Notifications. **This feature is in Limited GA.** | | CDS\_SUPPORT\_HTTP\_HEADER\_HTTP\_STEP | Allows capturing HTTP response headers, including cookies, as output variables in the HTTP step for use in downstream steps. **This feature is in Limited GA.** | | CDS\_SCM\_FIX\_FOLDER\_PATH | Fixes file copy issues in SCM integrations where a leading `/` in the source path caused only a single file to be copied instead of the entire directory. **This feature is in Limited GA.** | | CDS\_AWS\_CONNECTOR\_REF\_CDK | Expands the OIDC payload for GCS Cache steps to include additional claims, enabling fine-grained access control using custom claim attributes. **This feature is in Limited GA.** | | CDS\_AWS\_LAMBDA\_ROLLBACK\_V2 | Allows deployment of AWS Lambda artifacts larger than 50 MB from S3 and supports version rollback using aliases. **This feature is in Limited GA.** | | CI\_ENABLE\_MULTILINE\_OUTPUTS\_SECRETS | Enables support for capturing multiline output variables from Container steps in CD pipelines, ensuring proper population and visibility in the Output tab. **This feature is in Limited GA.** | | PIPE\_USE\_ORIGINAL\_YAML\_FOR\_EXECUTION | Enables re-running pipelines with the original pipeline definition and inputs to ensure accurate reproduction and debugging of historical executions. **This feature is in Limited GA.** | | PIPE\_ADD\_ORIGINAL\_FAILED\_CHILDREN\_TO\_OUTPUT | Fixes rollback handling for user-initiated failures and approval rejections by ensuring rollback strategies execute as expected. **This feature is in Limited GA.** | | CDS\_REMOVE\_COMMENTS\_FROM\_VALUES\_YAML\_WITH\_ESCAPE\_CHARACTERS | Enables proper handling of special characters in `values.yaml` by removing control characters such as `single (' )`, `double (")`, and `backslash (\)`, preventing pipeline failures. | | CDS\_ENFORCE\_GIT\_EXPERIENCE | Enables users to enforce the **Git experience for environments, infrastructure, and overrides V2**, ensuring consistency across all components, similar to pipelines, inputs, and templates. **This feature is in Limited GA** | | CDS\_TAS\_ARTIFACT\_BUNDLE\_PRESERVE\_PERMISSION\_ON\_EXTRACTION | Ensures that file permissions inside the `tar.gz` archive are retained when deploying **Artifact Bundles** for **NodeJS apps** to **PCF (Pivotal Cloud Foundry)**, preventing permission issues during application startup. **This feature is in Limited GA** | | CDS\_AZURE\_CLI\_WEBAPP\_DEPLOYMENT | Enables enhanced support for non-standard configurations and Azure CLI-based workflows for Azure Web App deployments. Available with Delegate version `85302` or later. **This feature is in Limited GA** | | CDS\_ECS\_MONITOR\_TASK\_STATUS | Enables Harness to accurately detect failures in **ECS Rolling Deployments**. **This feature is in Limited GA** | | PIPE\_USE\_HARNESS\_CODE\_FOR\_INLINE\_ENTITIES | Saves inline entities in the [Harness Code Repository](/code-repository/new-to-harness-code/onboarding-guide.md) by default. **This feature is in Limited GA** | | PIPE\_DYNAMIC\_PIPELINES\_EXECUTION | Allows users to dynamically execute pipelines by providing pipeline YAML configurations at runtime, without requiring pre-saved configurations in Harness. **This feature is in Limited GA** | | PIE\_USE\_OPTIMISED\_TEMPLATE\_RESOLUTION | Introduces the `storeType` field in YAML templates to distinguish whether a template is stored **Inline** or **Remote**. **This feature is in Limited GA** | | OPA\_IMPORT\_FROM\_GIT | Enables users to import OPA policies directly from Git. **This feature is in Limited GA** | | CDS\_GITOPS\_OPERATOR | Enables integration of the Harness GitOps Agent with the OpenShift Certified Vendor Catalog, allowing seamless use with OpenShift OperatorHub and Red Hat Marketplace. **This feature is in Limited GA** | | CDS\_K8S\_CUSTOM\_YAML\_PARSER | Enables support for Kubernetes sidecar containers as introduced in Kubernetes 1.28. This custom YAML parser addresses compatibility issues with the current Kubernetes Java SDK version 18.0.0, which lacks native support for sidecar configurations. **This feature is in Limited GA** | | CDS\_SKIP\_INSTANCES\_V2 | Enables users to retry failed deployments on a subset of hosts when using traditional infrastructure. **This feature is in Limited GA** | | CDS\_ECS\_BG\_VALIDATION\_WITH\_SAME\_TARGET\_GROUPS | Enables users with dynamically generated load balancer configurations to successfully validate ECS Blue-Green deployment pipelines, resolving the previous validation failure. **This feature is in Limited GA** | | CDS\_CROSS\_SCOPED\_ENV\_GROUPS | Enables users to add environments created at Account and Orgainsation level to Environment Groups. For more information, go to Harness [Cross Scope Environment Groups](/continuous-delivery/use-continuous-delivery/cd-building-blocks/environments/create-environment-groups.md#cross-scope-environment-groups). **This feature is in Limited GA** | | CDS\_K8S\_DETAILED\_LOGS | Enables users to view detailed logs of **Wait For Steady State** step in Kubernetes deployments. For more information, go to Harness [Detailed diagnostics for K8s Deployment](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/kubernetes-cd-quickstart.md#detailed-diagnostics-for-k8s-deployment). **This feature is in Limited GA** | | CDS\_SERVICE\_OVERRIDES\_2\_0\_YAML\_V2\_SUPPORT | Ensures that overrides from environment configuration YAML are ignored when Override V2 is enabled. This feature is in Limited GA. | | CDS\_AWS\_EKS\_CLUSTER\_MANUAL\_CONFIGURATION | Enables users to manually configure the connection to Amazon EKS clusters by providing the endpoint and optional CA cert. This feature is in Limited GA. | | CDS\_ENABLE\_RAW\_MODE | This feature requires enabling an Account-level setting after the Feature Flag is enabled. When this setting is disabled, blank fields are treated as Null. Enabling this option will treat blank fields as empty strings. Please be aware that this change may be disruptive to existing Input Sets. | | To learn more, refer [Handling empty strings](/harness-ai/use-harness-platform/pipelines/input-data-preprocessing.md). This feature is in Limited GA. | | | CDS\_AUTH\_CHECK\_IN\_WEBHOOK\_DETAILS\_ENDPOINTS | Enables users to track deployment status programmatically via REST using the apiUrl from a custom trigger's JSON response. This feature is in Limited GA. | | CDS\_PIPELINE\_ABORT\_RBAC\_PERMISSION\_MIGRATION | Enables users to run RBAC validation before executing inline pipelines to ensure access to required environments and resources. This feature is in Limited GA. | | CDS\_PIPELINE\_ABORT\_RBAC\_PERMISSION | Enables users to control Abort permission separately from other pipeline execute functions. This Feature is in Beta. | | CDS\_EVENT\_BRIDGE\_WEBHOOK and CD\_TRIGGERS\_REFACTOR | Enables users to trigger pipelines in real time using the newly introduced EventBridge webhooks, which can be configured with Git, Slack, or generic options (such as Nexus artifacts). This feature is in Limited GA. | | PIPE\_ENABLE\_FILE\_UPLOAD\_AS\_RUNTIME\_INPUT | Enables users to upload files as a runtime input during execution of a pipeline using **File Upload** step. This feature is in Limited GA. | | CDS\_ENCODE\_API\_REQUESTS | Enables users to fetch an artifact version from Nexus during deployment. This feature is in Limited GA. | | CDS\_EMAIL\_USE\_DEFAULT\_FORMATTING | Enables user to send HTML content in the email body in the **Email Step**. This feature is in Limited GA. | | CDS\_K8S\_SANITIZE\_COMPLETE\_DRY\_RUN\_STEP\_OUTPUT | Enables users to access Kubernetes service and job names in the exported manifest. This feature is in Limited GA. | | CDS\_K8S\_ASYNC\_STEP\_STRATEGY | Enables users to view log details in the UI when a pipeline with K8s async steps times out. This feature is in Limited GA. | | CDS\_ASG\_ROLLOUT\_ROLLBACK\_INSTANCE\_REFRESH | Enable this feature to eliminate downtime during the Auto Scaling Group (ASG) rollback instance refresh. This feature is in Limited GA. | | CDS\_SPECIFY\_INFRASTRUCTURES | Enables users to select all the infrastructures in the environment by choosing the **All Infrastructures** checkbox. This feature is GA. | | PIPE\_FILTER\_EXECUTIONS\_BY\_GIT\_EVENTS | This enables users to view both manual executions and those triggered automatically by Git pull requests (PRs) in the My Executions filter on the listing page. Executions triggered by GitHub PRs, as well as manually triggered pipeline executions, will appear in the My Executions list. This feature is in Limited GA. | | PIPE\_MARK\_PARENT\_PIPELINE\_STATUS\_WAITING\_AS\_CHILD | Enables users to see both the parent and child pipeline statuses as "Waiting" when the child pipeline is in a wait step during pipeline chaining, instead of having the parent pipeline show as **Running** while the child shows as **Waiting**. This feature is in Limited GA. | | CDS\_LIST\_REPO\_V2 | Enables users to search for repositories with infinite scroll support in a specific connector. By entering any keyword, related repositories will be displayed. If the desired repository is not found, users can also add it manually. This feature is in Limited GA. | | ENV\_GROUP\_DEPLOYMENTS\_IN\_SERIAL | Enables users to use the serial deployment of environment groups. This feature is in Limited GA. | | CDS\_DISABLE\_FALLBACK\_EXPRESSION\_ENGINE | Enables users to leverage the updated expression resolution fallback logic, which now calls the fallback more effectively. This feature is in Limited GA. | | GITOPS\_GET\_APP\_DETAILS\_STEP | Enables users to fetch the details and status of their application. This feature is in Limited GA. | | CDS\_HELM\_STEADY\_STATE\_CHECK\_1\_16 | Allow users leveraging Kubernetes version 1.16 or later to perform steady state check for Helm deployments. This feature is in Limited GA. | | OPA\_PIPELINE\_GOVERNANCE | Enables [Policy as code](/harness-ai/use-harness-platform/governance/policy-as-code/harness-governance-overview.md) for a Harness account. This feature is GA. | | NG\_PIPELINE\_TEMPLATE | Enables [Harness templates](/harness-ai/use-harness-platform/templates/create-pipeline-template.md). This feature is Limited GA. | | OPA\_GIT\_GOVERNANCE | Store and fetch your [OPA policies in Git.](/harness-ai/use-harness-platform/governance/policy-as-code/configure-gitexperience-for-opa.md). This feature is Limited GA. | | NG\_CUSTOM\_STAGE | Enables the[Custom stage](/harness-ai/use-harness-platform/pipelines/add-a-stage.md#add-a-custom-stage) for use in a pipeline. This feature is GA. | | NG\_GIT\_EXPERIENCE | Enables [Harness Git Experience](/harness-ai/use-harness-platform/git-experience/configure-git-experience-for-harness-entities.md) for a Harness account. Users can manage their Pipeline, Templates, Input Sets, Feature Flags via Git. This feature is GA. | | CDP\_USE\_OLD\_GIT\_SYNC | Enables the previous, deprecated version of Git Experience. This flag is only enabled for customers who have not migrated over to [Harness Git Experience](/harness-ai/use-harness-platform/git-experience/configure-git-experience-for-harness-entities.md). | | CDS\_DISABLE\_HELM\_REPO\_YAML\_CACHE | Disables Helm repository caching on the Harness Delegate. This should only be enabled if users are experiencing failures with Harness Delegate failing to fetch Helm Charts. Caching could be the source of the issue. This Feature is in Beta. | | CD\_GIT\_WEBHOOK\_POLLING | Enables configurable polling for [GitHub Webhooks](/harness-ai/use-harness-platform/triggers/triggering-pipelines.md) This allows users to set polling interval for Harness Delegate to poll your GitHub instance. This feature is in Limited GA. | | CDS\_DISABLE\_WINRM\_COMMAND\_ENCODING\_NG | Prevents the encoding of WinRM commands. By default Harness encodes the winrm commands we run on hosts. User's can disable this behavior via this feature flag. This feature is in Limited GA. | | CDS\_TERRAFORM\_S3\_SUPPORT | Enables AWS S3 for Terraform plan storage. This feature flag is Limited GA. | | CDP\_USE\_K8S\_DECLARATIVE\_ROLLBACK | Enables the [declarative rollback](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-k8s-ref/kubernetes-rollback.md#declarative-rollback) behavior for services. This feature is in Beta. | | CDS\_K8S\_SOCKET\_CAPABILITY\_CHECK\_NG | Replaces the HTTP capability check for the Kubernetes connector with socket capability. This feature is in Beta. | | PIE\_USE\_SECRET\_FUNCTOR\_WITH\_RBAC | Performs RBAC check on secrets when used in pipeline execution. This feature is in Beta. | | CDS\_GIT\_CONFIG\_FILES | Enables config files to be [managed in Git.](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/cd-services-config-files.md) | | PIE\_GITX\_OAUTH | Uses users' OAuth credentials to fetch and commit in Git. This feature is in Limited GA. | | PIE\_MULTISELECT\_AND\_COMMA\_IN\_ALLOWED\_VALUES | Enables the ability to [choose multiple values from a list of allowed values.](/harness-ai/use-harness-platform/variables-and-expressions/runtime-inputs.md#multiple-selection) | | CDS\_SUPPORT\_HPA\_AND\_PDB\_NG | Enables [PDB and HPA tracking](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-k8s-ref/what-can-i-deploy-in-kubernetes.md#managed-workloads-table) as managed resources by Harness. This feature is in Limited GA. | | CDS\_SSH\_SSHJ | Enables a library upgrade for SSH Deployments to use newer algorithms of SSH to connect to hosts. All Delegates on 803xx Release will have the new upgraded library. This feature is Limited GA. | | CDS\_SSH\_CLIENT | Enables a library upgrade for SSH Deployments to use newer algorithms of SSH to connect to hosts. All Delegates on 803xx Release will have the new upgraded library. This feature is Limited GA. | | CDS\_SERVICE\_OVERRIDES\_2\_0 | Enables [overrides v2 experience](/continuous-delivery/use-continuous-delivery/cd-building-blocks/overrides-v2.md). This feature is in Beta. | | CDS\_HELM\_STEADY\_STATE\_CHECK\_1\_16\_V2\_NG | Enables steady state check for Helm deployments on Kubernetes clusters using 1.16 or higher. This feature is in Beta. | | CDS\_RESOLVE\_OBJECTS\_VIA\_JSON\_SELECT | Support resolution of objects via the JSON Select Command in the HTTP step. This feature is in Beta. | | CDS\_ENABLE\_LOAD\_FROM\_CACHE\_FOR\_RETRY\_FORM | Enables a load from cache option on pipeline execution retry form. This feature is in Beta. | | CDS\_RECONFIGURE\_JIRA\_APPROVAL\_TIMEOUT | Reduces timeout for Jira from 5 minutes to 1 minute and allows pausing of approval. This feature is in Beta. | | CDS\_NG\_SERVICE\_PRINCIPAL\_FOR\_CUSTOM\_WEBHOOK | Makes authenticated custom Webhook calls use the service principal instead of the principal inherited from the API key. This feature is in Beta. | | OPA\_AIDA\_WIDGET | Enables [Harness AI for OPA](/harness-ai/use-harness-platform/governance/policy-as-code/ai-for-policies.md). This feature is in Beta. | | PIE\_SIMPLIFY\_LOG\_BASE\_KEY | Reduces the length of the log base key. This feature is in Beta. | | This feature requires delegate version 23.10.81010 or later. | | | After enabling this feature flag, you must re-run your pipelines to apply the change. | | | For more information, go to [Download execution logs](/harness-ai/use-harness-platform/pipelines/executions-and-logs/download-logs.md). | | | PIE\_ASYNC\_FILTER\_CREATION | Sets pipeline CRUD calls to filter creation asynchronously. This feature is in Beta. | | CDS\_CONTAINER\_STEP\_GROUP\_RUN\_AS\_USER\_AND\_PRIVILEGED\_FIX | Enable this feature if you want updated logic for permissions inheritance between steps and their step groups. To learn more go to [Step Group Inheritance Logic](/continuous-delivery/troubleshooting-and-resources/knowledge-base-article/configuration-inheritance-stepgroup-step.md). This is a Beta feature. | | CV\_MONITORED\_SERVICE\_TEMPLATIZATION | Enable this feature if you want to select a monitored service template as a runtime input. To learn more, go to [Select a monitored service template during runtime](/continuous-delivery/use-continuous-delivery/verify-deployments/configure-cv/simple-verification.md). This is a Beta feature. | | CDS\_ASYNC\_EXECUTABLE\_USE\_SELECTORS | When enabled the delegate selector priorities are correctly handled in Helm Blue/Green and Canary Deployment steps. This is a Beta feature. | | CDS\_NAV\_MODULE\_VISIBILITY | When enabled Admin users can hide unsubscribed modules from the sidebar, ensuring only subscribed modules are visible to team members. This helps streamline the user experience and prevents access to steps or features from unsubscribed modules. This is a Beta feature. | | GITOPS\_FILTER\_PANE\_ENABLED | When enabled, GitOps users can create and save application filters in the GitOps Applications page. This is a Beta feature | | FF\_PIE\_SET\_ADVISORS\_PROCESSED | When enabled the calculation of `<+stage.CurrentStatus>` exclude steps where the failure strategy has not yet been triggered. This ensures that steps are not prematurely skipped due to transient failure states, resulting in more reliable execution. This is a Beta feature. | | CDS\_EXECUTION\_LIST\_FILTERS | Enable this feature to improve filter UI on the execution list view. Use the new UI to add filter parameters, make custom filters, and save them, easier than before. **This is a Beta feature**. | | CDS\_AWS\_LAMBDA\_ROLLBACK\_V2 | When enabled, users can deploy Lambda artifacts larger than 50 MB stored in S3 **This is a Beta feature**. | | CDS\_GITLAB\_TRIGGER\_TAG\_EVENT | When enabled, u​sers can trigger pipelines in GitLab upon the creation or pushing of tags. **This is a Beta feature**. | | CDS\_INCLUDE\_EMPTY\_VALUE | When enabled, this will allow empty values to be accepted as an allowed value for runtime inputs. **This is a Beta feature**. | | PIPE\_FIX\_RESOURCE\_RESTRAINTS\_FOR\_RETRY\_STEPS | When enabled, this flag ensures that the existing `resourceRestraintInstance` is reused when a queue step is retried to fix an issue where multiple resource restraints were created for a single queue step. **This is a Beta fix** | | CDC\_SERVICE\_DASHBOARD\_REVAMP\_NG | Adds a **Metrics** tab to the individual service dashboard, showing deployments, failure rate, deployment frequency, active service instances, and the underlying environment and infrastructure over a selected period. **This feature is in Limited GA.** | | CDP\_USE\_K8S\_DECLARATIVE\_ROLLBACK\_NG | Enables declarative rollback for Kubernetes deployments. **This feature is in Limited GA.** | | CDS\_AIDA\_SUPPORT\_DEFLECTION | Enables AI-assisted support deflection (AIDA). **This feature is in Limited GA.** | | CDS\_ALLOW\_ACTIVE\_FREEZE\_EDIT | Editing active freeze windows through the API is blocked by default. Enable this flag to restore the previous behavior that allowed active freeze windows to be edited through the API. **This feature is in Limited GA.** | | CDS\_ARTIFACTORY\_OIDC\_AUTHENTICATION | Adds OIDC authentication to the Artifactory connector, enabling credential-free federated authentication with JFrog Artifactory using short-lived JWT tokens. **This feature is in Limited GA.** | | CDS\_ASG\_FIX\_LIFECYCLE\_HOOKS\_ORDER | Fixes a race condition where Auto Scaling Group (ASG) instances could launch before lifecycle hooks were added, causing inconsistent deployment behavior. **This feature is in Limited GA.** | | CDS\_ASG\_SKIP\_INSTANCE\_HEALTH\_CHECK\_BEFORE\_INSTANCE\_REFRESH | Fixes issues that occurred while skipping health checks for ASG instances before an instance refresh. **This feature is in Limited GA.** | | CDS\_AUTO\_APPROVAL | Enables automatic approval for pipeline approval steps. **This feature is in Limited GA.** | | CDS\_AWS\_STS\_NON\_DEFAULT\_REGION | Fixes an issue where AWS connectors using OIDC authentication failed to validate in non-default regions such as `af-south-1` (Africa South 1). **This feature is in Limited GA.** | | CDS\_AZURE\_CONTAINER\_APPS | Enables deployment to **Azure Container Apps** directly from Harness CD, with canary deployments, progressive traffic shifting, automatic rollback, and OIDC or key-based authentication. **This feature is in Limited GA.** | | CDS\_CONTAINER\_STEP\_GROUP\_REJECT\_NESTED\_INFRA | Enables backend validation to reject invalid YAML configurations where a containerized step group contains a nested step group as a container or includes a run step inside a nested step group, matching frontend validation restrictions. **This feature is in Limited GA.** | | CDS\_CONTAINER\_STEP\_GROUP\_STAGE\_TIMEOUT | Enables adding Approval steps inside Container Step Groups in CD pipelines, and automatically extends pod TTL when the stage timeout exceeds 24 hours. **This feature is in Limited GA.** | | CDS\_CONTAINER\_STEP\_USE\_STAGE\_IDENTIFIER | Fixes intermittent failures of the Wiz security scanning step in containerized step groups by setting the StageId to the stage name instead of a UUID. **This feature is in Limited GA.** | | CDS\_CUSTOMIZE\_PIPELINE\_TTL | Enables a customizable retention period (TTL) for pipeline cache entities. **This feature is in Limited GA.** | | CDS\_CV\_DYNATRACE\_GRAIL\_LOGS\_ENABLED | Adds support for Dynatrace Grail Logs as a health source for deployment verification. **This feature is in Limited GA.** | | CDS\_CV\_HEALTH\_SOURCES\_ENABLED | Enables Health Sources V2 and the Config Agent flow for Datadog metric and log health sources in Continuous Verification (AI Verify). **This feature is in Limited GA.** | | CDS\_CV\_MS\_GITX | Enables storing monitored services in Git using GitX, adding version control and code review workflows for verification configurations. **This feature is in Limited GA.** | | CDS\_CV\_SUB\_TASK\_CUSTOM\_WEBHOOK\_NOTIFICATIONS\_ENABLED | Adds custom webhook notifications for Continuous Verification sub-tasks, providing real-time updates on data collection, analysis, and verification status with correlation IDs. **This feature is in Limited GA.** | | CDS\_DISABLE\_CONNECTOR\_PT\_CREATION | Fixes an issue where editing a connector reset the Heartbeat Perpetual Task; the Perpetual Task is now properly deleted during connector edits. **This feature is in Limited GA.** | | CDS\_DISABLE\_FABRIC8\_NG | Fixes pipeline failures that occurred when Fabric8 was disabled through this flag. **This feature is in Limited GA.** | | CDS\_ECS\_BG\_VALIDATION | Enables blue-green validation for Amazon ECS deployments. **This feature is in Limited GA.** | | CDS\_ECS\_SCHEDULED\_ACTIONS | Adds support for **ECS Scheduled Actions** as a new manifest type (`EcsScheduledActionDefinition`) in ECS service deployments, enabling time-based auto-scaling policies. **This feature is in Limited GA.** | | CDS\_ECS\_SKIP\_APPLICATION\_SCALING | Adds a **Skip application auto scaling** option to ECS Rolling deployments, letting you manage auto-scaling externally and avoid AWS API rate limits. Requires delegate version `26.05.89205` or later. **This feature is in Limited GA.** | | CDS\_ENABLE\_INFRA\_HOST\_GROUPS | Adds support for **Host Groups** in Physical Data Center (PDC) WinRM deployments, letting you assign independent WinRM credentials to different groups of hosts within a single infrastructure definition. **This feature is in Limited GA.** | | CDS\_ENABLE\_PIPELINE\_SCOPED\_OIDC\_SUB | Fixes an issue where the OIDC sub claim did not include the pipeline ID for containerized step group executions. **This feature is in Limited GA.** | | CDS\_ENABLE\_SERVICE\_ON\_RUN\_OPA\_EVAL | Enables selecting the **Service** entity for both **On Run** and **On Save** events when creating an OPA policy set. **This feature is in Limited GA.** | | CDS\_ENABLE\_VM\_CONTAINER\_STEP\_GROUP\_INFRA | Adds support for VM infrastructure in containerized step groups, letting you run supported CD steps on Linux VMs instead of Kubernetes clusters. **This feature is in Limited GA.** | | CDS\_ENV\_LISTING\_RBAC\_IMPROVEMENT | Fixes an issue where service accounts with view permission were unable to list project environments. **This feature is in Limited GA.** | | CDS\_ESCAPE\_ENV\_VARS\_FOR\_WINRM\_KERBEROS\_NG | Fixes WinRM command and artifact download failures caused by improper handling of environment variables containing special or illegal XML characters (for example, `\`, `$`) when using Kerberos authentication. **This feature is in Limited GA.** | | CDS\_GITOPS\_DELEGATE\_USE\_SCM\_FOR\_COMMIT | Optimizes the performance of the Update Release Repo and Merge PR steps to reduce execution time for large repositories. **This feature is in Limited GA.** | | CDS\_GITOPS\_ENABLE\_ENV\_PROPAGATION\_UX | Fixes an issue where environment propagation between stages in GitOps PR pipelines failed with validation errors. **This feature is in Limited GA.** | | CDS\_GITOPS\_SECRET\_RESOLUTION\_ENABLED | Enables Harness secret expressions (`<+secrets.getValue()>`) directly in Kubernetes manifests, resolving and decrypting secrets during manifest rendering for Kubernetes `Secret` objects. Also lets you reference Harness secrets for GitOps cluster credentials when you register a cluster. **This feature is in Limited GA.** | | CDS\_HELM\_BG\_STRATEGY | Adds native support for **Canary** and **Blue-Green** deployment strategies with Helm chart deployments. **This feature is in Limited GA.** | | CDS\_HELM\_MULTIPLE\_MANIFEST\_SUPPORT\_NG | Enables configuring multiple Helm charts in service manifests and migrating services with Helm charts from FirstGen to NextGen, providing feature parity with Harness FirstGen. **This feature is in Limited GA.** | | CDS\_HTTP\_STEP\_NG\_CERTIFICATE | Lets you select secrets for a valid TLS certificate and key in the HTTP step for TLS connections. **This feature is in Limited GA.** | | CDS\_K8S\_PATCH\_STEP\_NG | Adds a **Patch** step for Kubernetes deployments to modify specific resources or workloads without affecting other fields, providing parity with the Spinnaker Kubernetes Patch stage. **This feature is in Limited GA.** | | CDS\_MANUAL\_INTERVENTION\_CUSTOM\_ACTIONS | Lets pipeline designers customize which actions (for example, Retry, Rollback) are available to the executor for Manual Intervention failure strategies. **This feature is in Limited GA.** | | CDS\_NG\_CONFIG\_FILE\_EXPRESSION | Enables the use of Harness expressions in config files. **This feature is in Limited GA.** | | CDS\_NG\_CONVERT\_BRANCH\_TO\_PUSH\_WEBHOOK\_BITBUCKET\_ON\_PREM | Makes triggers for on-premises Bitbucket capture branch hook events and convert them, on a best-effort basis, to push hooks so triggers fire on the first push to a new branch. **This feature is in Limited GA.** | | CDS\_NG\_TRIGGER\_SELECTIVE\_STAGE\_EXECUTION | Enables selective stage execution for pipeline triggers. **This feature is in Limited GA.** | | CDS\_NOT\_ALLOW\_READ\_ONLY\_SECRET\_MANAGER\_TERRAFORM\_TERRAGRUNT\_PLAN | Fixes an issue where the Terraform Plan step failed when an account-level (read-only) secret manager was selected and this flag was enabled. **This feature is in Limited GA.** | | CDS\_OIDC\_AWS\_SESSION\_TAGS | Adds environment identifiers as session tags in OIDC tokens for AWS connectors, enabling environment-specific IAM policy enforcement for resources and secrets. **This feature is in Limited GA.** | | CDS\_OVERRIDES\_VARIABLE\_NAME\_VALIDATIONS | Adds validation for override variable names, rejecting names that begin or end with a space or contain special characters. This is a breaking change for already-saved invalid variable names. **This feature is in Limited GA.** | | CDS\_PRESERVE\_WINRM\_WORKING\_DIR\_FOR\_COMMAND\_UNITS | Fixes an issue so that Harness uses the working directory you specify in WinRM script units. **This feature is in Limited GA.** | | CDS\_ROLLBACK\_IN\_STEPGROUP\_MANUAL\_INTERVENTION | Enhances rollback support so that rolling back a stage through manual intervention on a Run step failure executes the rollback stage action instead of failing. **This feature is in Limited GA.** | | CDS\_SAVE\_EXECUTION\_EXPRESSIONS | Displays the execution context, inputs, and outputs for each step on the Execution Details page to help debug pipeline executions. **This feature is in Limited GA.** | | CDS\_SECRET\_MANAGER\_DELEGATE\_SELECTOR\_PRECEDENCE | Fixes an issue in multi-account AWS setups so that a secret manager's delegate selector takes precedence over the connector's delegate selector, preserving environment IAM isolation. **This feature is in Limited GA.** | | CDS\_SERVICENOW\_TICKET\_TYPE\_V2 | Enables version 2 of ServiceNow ticket type support. **This feature is in Limited GA.** | | CDS\_SERVICE\_AND\_INFRA\_STEP\_DELEGATE\_SELECTOR\_PRECEDENCE | Fixes delegate selection so that stage-level and pipeline-level delegate selectors take precedence in Service and Infrastructure steps. **This feature is in Limited GA.** | | CDS\_SHARED\_SESSION\_WINRM\_NTLM\_NG | Adds WinRM session pooling for traditional Windows deployments, reusing idle sessions with matching credentials to save connection setup time. Supports NTLM authentication. **This feature is in Limited GA.** | | CDS\_SKIP\_CDK\_DEPLOY\_IF\_NO\_DIFF | Automatically skips AWS CDK Deploy steps when a preceding CDK Diff step detects no infrastructure changes, reducing deployment time. **This feature is in Limited GA.** | | CDS\_SKIP\_INVALID\_SHA\_DIGEST\_CHECK | Fixes an issue where artifact image SHA256 validation failed after moving a project to a different organization or account. **This feature is in Limited GA.** | | CDS\_STORE\_PRUNING\_RELEASE\_HISTORY\_IN\_SECRET | Stores Kubernetes release history in Secrets instead of ConfigMaps when pruning is enabled, providing a more secure storage mechanism. **This feature is in Limited GA.** | | CDS\_TAS\_LOGIN\_OPTIMIZATION | Fixes an issue where TAS rolling deployments failed for newly created apps with a "No API endpoint set" error. Requires delegate version `859xx` or later. **This feature is in Limited GA.** | | CDS\_USE\_CACHED\_REPOSITORY\_SUFFIX | Fixes artifact fetching from JFrog Artifactory Edge nodes by falling back to transitive search queries when standard queries return no results. **This feature is in Limited GA.** | | GITOPS\_AGENT\_METRICS\_PORT | Fixes an issue where the GitOps agent metrics server did not initialize correctly, ensuring the correct metrics port is set when metrics are enabled. Requires gitops-helm chart `1.1.16` (or `1.3.5` for `gitops-helm-byoa`). **This feature is in Limited GA.** | | GITOPS\_APPLICATIONSET\_FIRST\_CLASS\_SUPPORT | Adds first-class support for ApplicationSets, providing a scalable solution for multi-environment and multi-cluster GitOps deployments. **This feature is in Limited GA.** | | GITOPS\_BULK\_ACTIONS\_ENABLED | Adds **Bulk Sync** and **Refresh** buttons on the applications page so GitOps applications can be synced and refreshed in bulk. **This feature is in Limited GA.** | | GITOPS\_RESOURCE\_CLIENT\_CONNECT\_TIMEOUT\_SECONDS | Makes the connect timeout for GitOps app refresh calls configurable (for Self-Managed Platform customers, through the ng-manager override). **This feature is in Limited GA.** | | GITOPS\_RESOURCE\_CLIENT\_READ\_TIMEOUT\_SECONDS | Makes the read timeout for GitOps app refresh calls configurable (for Self-Managed Platform customers, through the ng-manager override). **This feature is in Limited GA.** | | NG\_DEPLOYMENT\_FREEZE\_OVERRIDE | Fixes an issue where triggers failed an RBAC permission check when the deployment freeze override was enabled. **This feature is in Limited GA.** | | NG\_OPTIMIZE\_FETCH\_FILES\_KUSTOMIZE | Optimizes fetching of Kustomize manifests for large repositories, adding an **Optimized Kustomize Manifest Collection** option. **This feature is in Limited GA.** | | NG\_SVC\_ENV\_REDESIGN | Enables the redesigned services and environments experience. **This feature is in Limited GA.** | | OPA\_ENABLE\_CANARY\_AI | Enhances Harness AI for OPA policies with the unified Harness AI agent, offering more accurate, context-aware policy generation and plain-language descriptions of existing policies. **This feature is in Limited GA.** | | PIE\_CONTAINER\_STEP\_ABORT\_USE\_UPSERT | Fixes an issue where container steps could get stuck when a ZTS denial occurred. **This feature is in Limited GA.** | | PIE\_FLEXIBLE\_TEMPLATES | Fixes visibility of the Edit (three-dots) button on the template details tab when using long template names. **This feature is in Limited GA.** | | PIE\_GITX\_EVALUATE\_ENCRYPTED\_CAPABILITIES | Works with `CDS_SECRET_MANAGER_DELEGATE_SELECTOR_PRECEDENCE` to fix AWS Secrets Manager connector validation so the secret manager's delegate selector takes precedence, preserving environment IAM isolation. **This feature is in Limited GA.** | | PIE\_NG\_BATCH\_GET\_TEMPLATES | Fixes an issue where templates could not be fetched from different repositories associated with the same SCM connector. **This feature is in Limited GA.** | | PIE\_PROCESS\_TRIGGER\_SEQUENTIALLY | Triggers a Git sync before executing associated triggers so pipelines run with the latest Git-synced configurations. **This feature is in Limited GA.** | | PIE\_USE\_LEGACY\_GIT\_ENTITY\_INFO | Fixes template resolution failures during pipeline retry when the template is stored in a non-default Git branch. This is an inverted flag: disable it to apply the fix. **This feature is in Limited GA.** | | PIPE\_ABORT\_ONLY\_TRIGGERED\_BY\_SAME\_TRIGGER | Fixes an issue so that a trigger only aborts executions started by the same trigger. **This feature is in Limited GA.** | | PIPE\_BULK\_RECONCILIATION | Adds bulk reconciliation of templates, letting you apply runtime input changes across multiple entities (such as stages or pipelines) in a single action. **This feature is in Limited GA.** | | PIPE\_CACHE\_CURRENT\_STATUS | Fixes incorrect failure strategy behavior where leaf steps skipped their immediate parent step group when updating cached status. **This feature is in Limited GA.** | | PIPE\_CRON\_TRIGGER\_AND\_SEMANTICS | Adds AND semantics to Cron triggers so that both date-range and day-of-week conditions must be satisfied simultaneously for complex scheduling. **This feature is in Limited GA.** | | PIPE\_DISABLE\_DEFAULT\_STORE\_TYPE\_TO\_INLINE\_FOR\_INPUT\_SET\_CREATE\_CHECK | Fixes an issue where users were unable to create overlay input sets due to an incorrect store type validation error. **This feature is in Limited GA.** | | PIPE\_DISABLE\_OPA\_GITCONFIG\_NEW\_BRANCH\_FIX | Fixes an issue where pipelines no longer sent Git configuration to Policy as Code. **This feature is in Limited GA.** | | PIPE\_DISABLE\_PARENT\_REPO\_NAME\_CONTEXT\_POPULATION\_FOR\_TEMPLATE | Fixes an issue where `parentEntityRepo` was incorrectly set to the template repo instead of the pipeline repo. **This feature is in Limited GA.** | | PIPE\_DISABLE\_PIPELINE\_CHAINING\_FOR\_FREE\_TIER | Enables gradual enforcement of pipeline chaining limits for the free tier without disrupting existing pipelines. **This feature is in Limited GA.** | | PIPE\_DISABLE\_TEMPLATE\_STABLE\_VERSION\_RACE\_CONDITION\_FIX | Fixes an issue where account-level templates displayed duplicate cards and incorrectly marked multiple versions as Stable, preventing deletion through the UI. **This feature is in Limited GA.** | | PIPE\_DISABLE\_THROWING\_ENGINE\_EXPRESSION\_EVALUATION\_EXCEPTION | Improves the "Unable to get secret information" error message to include the original secret name and scope so users can identify the missing or misconfigured secret. **This feature is in Limited GA.** | | PIPE\_DYNAMIC\_STAGE\_EXECUTION | Adds a new **Dynamic Stage** type that imports and executes pipeline YAML within a stage, where the YAML can be generated at runtime in a previous stage or provided directly. **This feature is in Limited GA.** | | PIPE\_ENABLE\_BARRIER\_STEPS\_SETUP\_OPTIMIZATION | Fixes an issue where pipelines with parallel stages could hang if a stage was skipped, causing barrier steps to never complete. **This feature is in Limited GA.** | | PIPE\_ENABLE\_DEPENDENCY\_BASED\_EXECUTION | Adds support for DAG (Directed Acyclic Graph) pipelines, letting you define explicit stage dependencies through the `dependsOn` field so that independent execution paths progress as soon as their dependencies finish. **This feature is in Beta.** | | PIPE\_ENABLE\_GITLAB\_ON\_PREM\_FLOW | Adds support for configuring OAuth for self-hosted GitLab providers. Requires Harness Delegate version `843xx` or later. **This feature is in Limited GA.** | | PIPE\_ENABLE\_QUEUE\_BASED\_PLAN\_CREATION\_FOR\_TRIGGER\_EXECUTIONS | Enables queue-based plan creation for trigger executions, used with Project-Level Pipeline Execution Concurrency. **This feature is in Limited GA.** | | PIPE\_ENABLE\_TRIGGER\_FAILED\_NOTIFICATION | Adds notifications for trigger failures, alerting users when a trigger fails to start a pipeline execution. **This feature is in Limited GA.** | | PIPE\_GITX\_DISABLE\_REPO\_URL\_FOR\_GIT\_CACHE | Uses the repository URL (repoURL) to perform cache lookups through the Git cache fetch method. **This feature is in Limited GA.** | | PIPE\_HONOR\_PIPELINE\_SDK\_PRIORITY\_IN\_EXECUTION\_URL | Fixes an issue where execution links incorrectly redirected to the IDP view in the Harness UI. **This feature is in Limited GA.** | | PIPE\_INSERT\_STAGE\_EXTENDED\_SUPPORT | Fixes inconsistent behavior of the **Insert Stage** functionality. **This feature is in Limited GA.** | | PIPE\_PIPELINE\_STAGE\_PIPELINE\_TEMPLATE | Fixes an issue where users were unable to create a template from a pipeline. **This feature is in Limited GA.** | | PIPE\_QUEUED\_PIPELINE\_OBSERVABILITY | Adds an **Executions Management** page for account-level visibility into queued pipeline executions, with queue positions, filtering by organization or project, and individual or bulk cancellation. **This feature is in Limited GA.** | | PIPE\_SHOW\_ALL\_EXECUTIONS\_ON\_ACCOUNT\_OVERVIEW\_PAGE | Shows all pipeline executions in the notification section regardless of module type (CI, CD, and so on), not only executions containing a CD stage. **This feature is in Limited GA.** | | PIPE\_SKIP\_EXECUTE\_WHEN\_CONDITION\_ON\_RETRY\_STEP | Fixes an issue so that a step's *When* condition is re-evaluated on each retry attempt, preventing incorrect execution after an initial evaluation failure. **This feature is in Limited GA.** | | PIPE\_TEMPLATE\_LABELS\_FEATURE | Adds **template labels** for referencing template versions using semantic names instead of fixed version numbers. **This feature is in Limited GA.** | | PIPE\_TRIGGER\_SCM\_FETCH\_THROW\_EXCEPTION | Requires PR triggers to use a Git connector with API access enabled; pipeline executions fail with an error if the connector does not have API access. **This feature is in Limited GA.** | | PIPE\_USE\_DYNAMIC\_MODULE\_TYPE\_IN\_BUILD\_DETAILS\_URL | Fixes an issue where the execution URL in Git status checks from Custom stages always pointed to a CI module path, showing a blank page for accounts without a CI license. **This feature is in Limited GA.** | | PIPE\_USE\_ENV\_REF\_BRANCH\_IN\_SERVICE\_OVERRIDE\_FOR\_INPUTSET\_TRIGGER | Improves the misleading error message shown during environment branch selection in service overrides when using InputSet triggers. **This feature is in Limited GA.** | | PIPE\_USE\_PIPELINE\_IDENTIFIER\_IN\_AUDIT\_LOGS | Uses the pipeline identifier in audit logs. If you enable this flag, update your integration points to accommodate the change. **This feature is in Limited GA.** | | PL\_GCP\_OIDC\_AUTHENTICATION | Adds support for custom attributes for OIDC with the GCP connector. **This feature is in Limited GA.** | | SPG\_DISABLE\_CUSTOM\_WEBHOOK\_V3\_URL | Lets you continue using the previous custom webhook trigger API (`v2`) instead of the new `/v3` token-based API. **This feature is in Limited GA.** | | CDS\_AGENT\_RUNTIME\_DEPLOYMENT | Enables [AI agent deployments](/continuous-delivery/use-continuous-delivery/ai-agents-deployment/overview.md) as a first-class deployment type, so you can deploy an Agent Service to AWS Bedrock AgentCore or Google Vertex Agent Runtime through the standard CD environment, infrastructure, and pipeline model. **This feature is in Beta.** | | CDS\_CLEAN\_NOTIFICATION\_EVENT\_TYPE | Fixes an issue where the notification event type intermittently contained infrastructure metadata instead of the event type in notification templates. The event type now resolves to the type alone, with a separate event details value for descriptive information. **This feature is in Beta.** | | CDS\_CV\_INPUT\_OUTPUT\_VARIABLES\_ENABLED | Enables the `customVerificationStartTime` configurable property in the [AI Verify (v1) step](/continuous-delivery/use-continuous-delivery/verify-deployments/configure-cv/verify-deployments.md), so you can shift the start of the verification window to an earlier timestamp. **This feature is in Beta.** | | CDS\_CV\_PER\_METRIC\_SENSITIVITY | Enables [per-metric sensitivity override](/continuous-delivery/use-continuous-delivery/verify-deployments/verify-deployments-with-the-verify-step.md#sensitivity) in the Verify step, so you can set the sensitivity (High, Medium, or Low) individually per metric instead of applying one setting to every metric in a health source. **This feature is in Beta.** | | CDS\_USE\_METADATA\_FOR\_CUSTOM\_DEPLOYMENT\_LIST | Optimizes Custom Deployment service and infrastructure list APIs by persisting the template version label and reference directly in entity metadata instead of fetching and parsing YAML from Git on every request. This significantly improves list performance for accounts with many remote Custom Deployment entities. **This feature is in Limited GA.** | | PIPE\_ENABLE\_OPA\_GOVERNANCE\_FOR\_AUTO\_CREATION, PIPE\_OPA\_GITX\_ENFORCEMENT, CDS\_OPA\_GOVERNANCE\_FOR\_WEBHOOK | Enforces [onSave OPA policies](/harness-ai/use-harness-platform/governance/policy-as-code/harness-governance-overview.md) on Git-backed entities, so a change committed directly to Git to a pipeline, template, service, environment, infrastructure definition, or override is evaluated against the onSave policy and blocks execution when the most recent commit fails the check. For pipelines and templates, execution is blocked at the pipeline level. For CD entities, the violation is surfaced on the entity detail page and execution is blocked at the step level when the entity is referenced. Go to [Enforce onSave policies on Git-backed entities](/harness-ai/use-harness-platform/governance/policy-as-code/enforce-policies-on-git-backed-entities.md) to configure. **This feature is in Beta.** | | PIPE\_ENFORCE\_TRIGGER\_EXECUTOR\_IDENTITY | Enables a [trigger executor identity](/harness-ai/use-harness-platform/triggers/trigger-executor-identity.md), so a pipeline started by a trigger runs with an associated user or service account and its RBAC permissions instead of the Harness system principal. **This feature is in Beta.** | | PIPE\_GITX\_FORCE\_REFRESH | Enables on-demand refresh of the [Git cache for remote entities](/harness-ai/use-harness-platform/git-experience/harness-git-cache.md) through the **Reload from Git** option or the refresh API, without waiting for a webhook. Refreshing an entity also reloads the caches of its referenced entities. **This feature is in Beta.** | | PIPE\_GITX\_RATE\_LIMITS\_API, PIPE\_GITX\_WEBHOOK\_HEALTH\_PER\_REPO | Enables the Observability views on the [Git Experience](/harness-ai/use-harness-platform/git-experience/git-experience-overview.md) Webhooks monitoring page, which monitor repository synchronization health and Git provider API rate-limit consumption. **This feature is in Beta.** | | PIPE\_MULTILINE\_VARIABLE\_INPUT | Enables [multi-line string input for custom variables](/harness-ai/use-harness-platform/variables-and-expressions/add-a-variable.md), so the value field for a pipeline-scoped or stage-scoped string variable becomes a resizable text area. **This feature is in Beta.** | | PIPE\_TEMPLATE\_OVERRIDES | Enables [template overrides](/harness-ai/use-harness-platform/templates/template.md), so a template owner can allow specific advanced settings to be overridden by callers without editing or duplicating the template. Supported for v0 YAML step, stage, step group, and pipeline templates. **This feature is in Beta.** | | PIPE\_USE\_COUNTER\_BASED\_STEP\_CONCURRENCY\_GATE | Enforces an [account-level step concurrency limit](/harness-ai/use-harness-platform/pipelines/pipeline-settings.md) that caps the total number of concurrently running steps across all pipeline executions in your account, in addition to the per-execution limit. **This feature is in Beta.** | | PIPE\_GRAPH\_VIEWPORT\_PERSISTENCE | Enables pipeline graphs to [open zoomed to fit by default and preserve the selected zoom level](/harness-ai/use-harness-platform/pipelines/pipeline-settings.md#pipeline-graph-zoom) per pipeline in the browser for Pipeline Studio and pipeline execution views. **This feature is in Beta.** |