Feature Requests

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're noticing a serious performance issue on the IACM approval step UI. When the page loads, it becomes extremely slow and eventually freezes making it nearly impossible to click the "Approve" or "Reject" buttons. We suspect this is due to the number of resources displayed on the page. Even though our change affects only 1 resource, the UI attempts to render all resources provisioned in that workspace (most of which are unchanged) - in our case it's more than 3000 resources, and this causes a significant performance degradation.

I want a private registry for our ORG and we should not be making connectors and secrets at the account level to access our org level material. this is not thought out well.

We should be able to run IaCM pipelines on our VM infrastructure. This is needed because many of our services that provide secrets and source code are located on-prem.

We request support for the Vault OIDC connector in IaCM workspaces in Harness. Currently, the Vault connector cannot be used within IaCM, limiting secure and centralized secrets management.

Support ARM64 pods to run Harness IACM pipelines We would like to use ARM64 pods to run Harness IACM pipelines, which requires the harness_terraform plugin ( https://hub.docker.com/r/plugins/harness_terraform/tags ) to support the ARM64 platform. Currently, we see that only an AMD64 image is available.

how we see in IaCM pipeline that which workspace it is used for running the pipeline to see in the execution history like in CD we have services and environment do we have anything in IaCM pipelines ???

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

Enhancements to the IACM approval step, specifically to align its functionality with the existing Harness Approval step. We are requesting for following key features: Email notifications to User groups: The ability to send email notifications containing details of the IACM plan step to specified user groups. Restricted Approval based on Executor: Implementation of a mechanism to prevent the user who executed the pipeline from approving the changes implemented by said pipeline. Dedicated Approval User Group: The ability to define a distinct and authorized user group responsible solely for approving IACM changes.

We request the ability to use the terraform_remote_state data source to reference outputs from one workspace in another, even when these workspaces reside in different organizations, using the Harness terraform backend with IaCM.