Feature Requests

In reference to this feature request: https://ideas.harness.io/feature-request/p/output-terraform-plan-init . I would like to see an option for the full terraform plan output and have it posted to a comment on a pull request. Currently we see something like this: ✅ Terraform plan complete! 🏢 Org: <...> 📖 Project: <...> Workspace: <...> Planned Changes 3 Added ~ 0 Changed ~ 0 Deleted ~ 826 Unchanged ~ 0 Imported ~ 0 Removed The table of planned changes can be viewed in Harness. Outputs No outputs present View details in Harness <--- This is a link to terraform I would like the option to enable full output, or at least some portion of the output if it is a very large plan. For small plans, it would take one less step to review the PR.

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

Hello, Currently, custom runner images can only be configured through YAML, as described in the Harness documentation: Harness Plugin Images Documentation: https://developer.harness.io/docs/infra-as-code-management/pipelines/plugin-images/ step: type: IACMTerraformPlugin name: apply identifier: apply timeout: 2h spec: command: apply image: plugins/private_harness_terraform_plugin # (1) connectorRef: privateConnector # (2) We would like to request the ability to add custom runner images directly through the UI, which would improve usability and reduce reliance on YAML configuration. Please let me know if you need any additional details or have questions regarding this request.

Module download stats not present in Harness IaCM Module registry

We’d like to request the addition of jq and other commonly used binaries to the default image used in Terraform and OpenTofu steps in IACM pipelines. Currently, in order to use tools like jq inside Terraform/Opentofu steps (within external data sources or local-exec scripts), we are forced to maintain a custom image just to include these basic binaries. This adds unnecessary overhead and complexity to our pipeline setup.

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.

Add a place to include usage examples with the modules in the registry. Similar to how these Google provided github modules provide examples: https://github.com/terraform-google-modules/terraform-google-network

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, 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

Currently in IACM Approval stage, only 1 approval is required to run terraform apply. Therefore in our current setup, we had to introduce another Manual Approval stage before terraform apply so that pipeline will continue only after 2 approvals for higher environments. So, we need a feature in IACM Approval stage to allow multiple approvals before terraform apply.