Feature Requests

We would like to request support for write-only arguments for sensitive fields used in the harness_platform_gitops_repository resource within the Harness Terraform provider. Currently, GitOps repository authentication credentials such as GitHub PATs or SSH private keys are persisted in the Terraform/OpenTofu statefile because the provider does not support write-only attributes for these fields.

The missing 'what': We have no centralized page to view current flag states across a project. The 'why' this is an issue: For large orgs, it can take a stakeholder too long to review the state of their products, clicking into each flag to see their targeting rules individually. A possible 'how' for fixing this: Provide a view or page including a chart/grid with flag state summaries including the name, environment, and treatment (if at 100% distribution) i.e. flag name | test-env | stage-env | prod-env ------------------------------------------------- test_flag | on | on | 2 rules ------------------------------------------------- ex-flag | on | 1 rule | off ------------------------------------------------- ui-config | 1 rule | dark | light

The serviceDefinition YAML of an service types K8s,ECS etc is not fully expanding to the harness pipeline YAML.

In the case where the customer has AppProjects that are unmapped and cannot be removed from the Argo instance. Below error is seen in agent logs ----- time="2026-04-28T10:53:06Z" level=error msg="Failed to create update event: project <project-name> is not mapped" accountId=<account-id> agentId=<agent-id> component=events disasterRecoveryId= entity=applications error="project <project-name> is not mapped" orgId= pid=1 projectId= version="" ------- Feature request to suppress these error entries in agent logs, as they might saturate the logs with excessive errors.

We use Notification Templates in Harness, and most of the templates have GIT experience, but notification template doesn't. We use GIT as our single source of truth. The matter of fact that these areas lacking GIT experience makes it difficult to maintain that DevOps principle. One must always remember to manually sync-up the changes between inline updates in Harness to GIT, making it difficult/confusing to determine which is the single source of truth from operational point of view.

Currently in the native helm deployment we do not have functionality to get the helm diff to compare against the live state of the helm chart. This can be achieved using this plugin - helm plugin install https://github.com/databus23/helm-diff Please add support for the helm diff in the native helm step, as it will be more useful to understand the actual changes getting deployed.

Hi Harness We need a delegator image with helm 3.17+ According to your dockerfile, the officical image is still using helm v3.15 https://github.com/harness/delegate-dockerfile/blob/main/Dockerfile We need helm v3.17+ to use this new --take-ownership param. In Helm, the --take-ownership flag is a feature introduced in Helm v3.17.0 (released January 2025) that allows a Helm release to claim management of Kubernetes resources that already exist in the cluster Can you make one for us?

Wanted to create the dashboard for policy and Governance therefore need the ability for this

I'd like to be able to set the OpenTofu version of a workspace to be the latest of a given release. For example, if I set the OpenTofu version to ~> 1.11 the workspace should use the latest release of OpenTofu in the 1.11.x releases. This would save me from having to ensure bugfix releases are updated on workspaces while still giving me control over potentially breaking changes.

Requesting a feature to define centralized drift control policies in Harness to customize what should be considered as drift across all Terraform pipelines. This should allow ignoring specific attributes or fields globally. Example: If a policy is set to ignore labels, then any drift caused only due to label changes should not be detected or trigger pipeline failures across all resources. This capability should be generic so we can control drift behavior as per the requirements without modifying individual Terraform code.