Feature Requests

We would like the ability to reference IACM Workspaces via tagging when creating Resource Groups. This will allow us to more effectively apply RBAC permissions and governance for workspaces between project within our Harness environment.

Tags in the tag filter are currently additive. So if I select environment:production and type:harness-project it returns all workspaces with either tag instead of only ones with both. Can we at least have a toggle for the behavior to make it filter for workspaces that have all of the selected filters? I think making that the default behavior is probably what most users would expect from a multi-select filter so I would prefer if it was just the default

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.

Currently, when "After Terraform Plan" policies are enforced in IaCM, the evaluation occurs in the background. While the results are visible under the "Policy Evaluations" tab, they do not appear as a distinct step in the pipeline execution flow. Problem: From a developer experience (DX) perspective, the pipeline execution can fail without an obvious step boundary. This lack of visibility makes it difficult for application teams to understand: That a policy check is actually occurring. Why the transition from "Plan" to "Apply" failed without digging into a separate tab. Suggested Enhancement: Introduce a visible "Policy Check" or "Governance" step in the execution UI between the Plan and Apply/Approval stages. This step should: Represent the OPA evaluation phase. Provide direct links to the violation details upon failure. Ensure the execution flow matches the logical intent: Plan → Policy Check → Apply. Impact: Improves transparency and self-service for app teams as we scale IaCM across large organizations where governance is enforced centrally. Customer Context: Account: World Fuel Services Reference: Zendesk Ticket 112569

There are cases where we need to perform both actions, LOCK and UNLOCK for any IACM workspace, can we convert that to a button, would be easy interface to interact with.

Add a harness connector so we can securely attach a harness service account to activities like IaCM without having to provision static keys that need to be passed around and rotated. This feature specifically is useful for us in IaCM but I would love to see this available for other things too such as the http request step in ci/cd for times when we want to call a harness api in a pipeline

Currently, Harness only supports string and secret type variables. We'd like to be able to define object type variables in our Terraform Workspace.

Module download stats not present in Harness IaCM Module registry

Hi Team, We are looking the find the list of all the infra created from Harness at one place with details like resource name, project, asset type. Can you please help us in this if this feature is already available? Regards, Hemanth Varma