Feature Requests

What: The IACMAnsiblePlugin step type only works with KubernetesDirect infrastructure (K8s delegate). It should also support Harness Cloud runtime, the same way IACMTerraformPlugin does. Current behavior: When you configure an IACM stage with IACMAnsiblePlugin using Cloud runtime (platform: Linux/Amd64, runtime: {type: Cloud}), the step fails immediately with "exit status 1" and no actionable error message. No logs, no explanation — just a silent failure. Expected behavior: The plugin should execute the playbook against reachable hosts (public IP, SSH open) from Cloud runtime, or at minimum return a clear error explaining why Cloud runtime is not supported. Why this matters: IACMTerraformPlugin already works on Cloud runtime — there's no reason the Ansible plugin shouldn't have parity. Many demo and dev environments have publicly reachable hosts. Requiring a persistent K8s delegate just to run Ansible adds infrastructure cost and complexity that isn't necessary when targets are reachable over the internet. The current workaround (Run steps with shell-scripted ansible) works but bypasses the native IaCM Ansible integration — no registered playbooks, no registered inventories, no visibility in the Harness UI. Reproduction steps: Create an IACM workspace with a registered playbook and inventory Create a pipeline with an IACM stage using Cloud runtime Add an IACMAnsiblePlugin step with command: run Execute — fails with exit status 1, no logs Environment: Harness SaaS, IaCM module, August 2026

Hi, We deleted our iacm_integration_testing pipeline by accident, could you provide us an sample pipeline yaml to recreate the pipeline. The pipeline as used to test all of the registered modules, which used the feature 'integration test for modules' so it save some cost for us. The input of the pipeline is module names but not work space. Thank you.

Please enable Ansible capabilities for our account.

We seems don't have license to run apply now in our sbox environment. Installing provisioner: opentofu Harness licence information: usage exceeds the limit for account: IYUbxLRTQzeDG_HnS3Ojug Account: IYUbxLRTQzeDG_HnS3Ojug Total 'apply' operations used : 70 Total 'apply' operations available : 25 [ERROR] the operation failed because the account is not licenced: usage exceeds the limit for account: IYUbxLRTQzeDG_HnS3Ojug

There is no Harness-published reference for how to build a Windows AMI with Ansible via IaCM. No troubleshooting guide. No known-good base image. We've engineered everything from scratch over six weeks of POC work that should have been two. Ask: A reference repo / docs page covering exactly this pattern.

It will be good to get a report of pipelines/workspaces running a specific version of Terraform module from registry and enforcing OPA for module version usage.

When trying to search for a provision pipeline - the execution history on the pipelines aren't saved for more than 30 days. inside the workspace I can get to pipeline executions that managed a workspace through the activity tab but when searching those there are many that say 'a month ago' etc. I want it to say 4/27/2026 so i know which day i'm searching for.

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

Description: Please add support for including workspace tags in the Policy On Save payload for IaCM workspaces. Problem When policies are evaluated on IaCM workspace save events, the payload does not currently include the tags defined on the workspace itself. Because of that, policies cannot validate or protect workspace tags during save operations. Why this matters Tags are often used to drive governance, automation, ownership, environment controls, and feature behavior. Without tag data in the policy input payload, it is not possible to create robust policies that: • require certain tags • block changes to protected tags • validate allowed tag values • enforce governance based on workspace metadata Requested enhancement Include the workspace’s tags in the On Save policy evaluation payload for IaCM workspaces. Expected outcome Policy authors should be able to reference workspace tags directly in policy inputs during save events and create policies that enforce tag presence, tag immutability, and tag-based controls. Impact Today, this creates a governance gap for IaCM workspaces because policies cannot evaluate one of the core metadata fields commonly used for controls and automation.

Currently, when running terraform plan in Harness, the -lock=true flag is enforced in the command, and attempts to override it via TF_CLI_ARGS_plan environment variable do not take effect. We attempted to override the -lock flag by setting TF_CLI_ARGS_plan=-lock=false both as an environment variable and as a stage variable. However, the argument shown in the command in step logs remains -lock=true, and the state still gets locked during the plan step. This will allow teams to control locking behavior during plan (e.g., disable locking for read-only plan runs while keeping it enabled for apply runs). Without this capability, plan steps in Harness unnecessarily lock the state, potentially blocking other operations.