Feature Requests

Couldn't see variable sets in Harness IACM Workspace after attaching by Terraform code Below are state file after successfully apply terraform code to attach variable set to Harness IACM Workspace: "type": "harness_platform_workspace", "name": "this", "variable_sets": [ "mgmt_shared_credentials_dev", "mgmt_hcv_shared_credentials_dev", "mgmt_shared_vault_token_dev", "mgmt_shared_credentials_vwan_dev" ] But we couldn't see variable sets in Harness IACM Workspace UI. Please help to check. https://nab.harness.io/ng/account/tnA9DBjWSIue1XjX_c-3Ww/all/iacm/orgs/et/projects/cps/workspaces/mgmt_g083_az_dev_int_spoke_1/variables

Enhance the Harness Workspace variable management experience by adding support for descriptions on variables. This will allow users to provide additional context about the purpose, usage, and expected values of workspace variables, improving readability, maintainability, and collaboration across teams. Requirements Add a Description field when creating or editing workspace variables. Display the description alongside variable details in the workspace UI. Support viewing and updating descriptions for existing variables. Ensure descriptions are stored and retrieved through the corresponding backend APIs. Maintain backward compatibility for variables that do not have descriptions.

Need sample code for iacm_integration_testing pipeline, which is use to test all the registered modules.

Hi, We deleted our iacm_integration_testing pipeline by accident, could you provide us an sample pipeline yaml to recreate the pipeline. The pipeline as used to test all of the registered modules, which used the feature 'integration test for modules' so it save some cost for us. The input of the pipeline is module names but not work space. Thank you.

Please enable Ansible capabilities for our account.

We need the Playbooks feature to source control Ansible roles/code scoped from Account level rather than at Project level.

We seems don't have license to run apply now in our sbox environment. Installing provisioner: opentofu Harness licence information: usage exceeds the limit for account: IYUbxLRTQzeDG_HnS3Ojug Account: IYUbxLRTQzeDG_HnS3Ojug Total 'apply' operations used : 70 Total 'apply' operations available : 25 [ERROR] the operation failed because the account is not licenced: usage exceeds the limit for account: IYUbxLRTQzeDG_HnS3Ojug

There is no Harness-published reference for how to build a Windows AMI with Ansible via IaCM. No troubleshooting guide. No known-good base image. We've engineered everything from scratch over six weeks of POC work that should have been two. Ask: A reference repo / docs page covering exactly this pattern.

The entire ansible-playbook invocation collapses into a single ansible_run step in the graph. A 50-task playbook surfaces as one node with one status. Even when we split a 30-minute "wait for AMI" loop into milestone tasks (25/50/75/100%), the pipe sees one Running for 30 minutes. Operations cannot tell whether the build is on Stage 1 or Stage 4. Ask: Per-task callbacks / progress events on the execution graph.

It will be good to get a report of pipelines/workspaces running a specific version of Terraform module from registry and enforcing OPA for module version usage.