Feature Requests

The Harness UI allows configuring an Azure Key Vault secret manager connector using delegate credentials — System-assigned or User-assigned Managed Identity — without storing an Azure client secret in Harness. The Terraform resource for the same connector currently treats client_id, tenant_id, and secret_key as required arguments. Passing null or omitting them for MSI-style configuration fails with errors such as: Error: Missing required argument The argument "client_id" is required, but no definition was found. The argument "tenant_id" is required, but no definition was found. The argument "secret_key" is required, but no definition was found. That forces ManualConfig-style usage in Terraform, where secret_key must reference the Harness Built-in Secret Manager, which conflicts with org policies that do not allow storing connector credentials in the harness built-in secret manager. Please update the Harness Terraform provider (and document behavior) so that harness_platform_connector_azure_key_vault match

It would be nice to be able to sort the terraform variables by name so they could be compared/lined up with other workspaces.

Currently we only get notification that workspace is drifted, but it would help us to know more details like its in drifted state from last 1 week/1 month/ 1year. Add-on details like what exact drift will be even useful.

There is support for most properties, but can we include tags as well? Currently, only these workspace expressions are supported : https://developer.harness.io/docs/infra-as-code-management/workspaces/workspace-expressions/ It will be of great use if something like <+workspace.tags.SOME_TAG> is available.

There are cases where we need to perform both actions, LOCK and UNLOCK for any IACM workspace, can we convert that to a button, would be easy interface to interact with.

Currently notifications setting are pipeline level, in cases where multiple workspaces share a common pipeline, need to send notifications to workspace specific settings. So notifications settings should be supported on workspace level, which should override pipeline level settings

Currently there is a big feature gap between IACM Approval and Harness Approval step. IACM approval should provide all the features of Harness Approval steps

The plan.json from a terraform plan is missing the workspace tags and repo information that could be used for OPA. This needs to be added given other workspace information is already included.

Hi Team, We need a Harness data source for Harness secrets with which we can call the existing harness secret values and pass it to the another terraform module. Regards, R Hemanth Varma

A few suggestions to make PR comments easier to use. First it would be to clean up outdated comments. If a PR goes through several iterations the comment thread get's long. Doing something like this action (maheshrayas/action-pr-comment-delete) does would help keep the SPAM in check. Second, it would be nice if the tables with the changes were in a <details> <summary> block that was shrunk down by default. This action does something like that with diffs int128/comment-action. Third, it would be nice if there was a bit more detail about what specifically changed with each resource when you run speculative plans so you don't have to read the plan log to understand the change details.