Feature Requests

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.

We want to create workspace templates for team to use to create workspace easily for each service to bring up infra. so i need just user input for directory path when they create workspace using the created workspace template. Creating a template for a repo and one directory doesnt serves a purpose. it only give user who uses template prefilled fields with no edit options.

We are looking for IACM dashbaords which can give us information like what all resources are deployed using IACM module at project/org/account level. Ex ask - If we can get a dashboard with some of the details below, it will be great. Project A, Cloud[AWS|GCP], [Account|Project] Id, Resource Type[EC2, GCE, RDS], Resource Name, Creation Date. At the minimum, I am looking for a report for EC2 and GCP instances along their names and creation date if that can be generated.

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.