Feature Requests

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.

Currently, the harness_terraform image does not have any third party binaries included. Users rely on custom images to hae these included https://developer.harness.io/docs/infra-as-code-management/pipelines/iacm-plugins/plugin-images/ . However, this causes an overhead of creating and managing custom images and the image gets overridden at the account level. The request is to have the binaries for azcli and other leading cloud provider clis such as aws,gcp

IACM doesn't have terraform import command , so in case we need to import resources in our statefile what is the best approach or is it possible to add the import command in the IACM .

Git submodule feature required on IaCM module, to support the custom providers being used in the application team code repository

We leverage an IACM Approval step in our IAC pipelines. Our customers would to like to receive notification once the IACM ( Terraform init / plan ) step is complete. The notification should have Terraform Plan output in it.

To creating a harness_platform_resource_group required the account_id. The provider already is scoped to the account so this is unnecessary. Also, the lack of a data source makes it hard to use these resources in a module.

Managing configuration in Terraform is cognitive overload. Feature request: An interactive GUI builder for making the changes you want and either exporting the Terraform configuration (to copy/paste) or syncing it back to the repo by opening a github pull request automatically.

Hi Team, Could you pleasde enable Harness Infrastructure as Code Management (IaCM) on my account for testing and understanding concept.

Inside of the my IACM module ideally I would only see the pipelines associated with my workspaces and not any pipelines for building my application source. This would help keep things cleaner. The same thing is true in that in my build module I also would not want to see the IACM pipelines.

Feature to display the "Review" button in the approval step when using chained pipelines.