P
Prospective Badger
What: The IACMAnsiblePlugin step type only works with KubernetesDirect infrastructure (K8s delegate). It should also support Harness Cloud runtime, the same way IACMTerraformPlugin does.
Current behavior: When you configure an IACM stage with IACMAnsiblePlugin using Cloud runtime (platform: Linux/Amd64, runtime: {type: Cloud}), the step fails immediately with "exit status 1" and no actionable error message. No logs, no explanation — just a silent failure.
Expected behavior: The plugin should execute the playbook against reachable hosts (public IP, SSH open) from Cloud runtime, or at minimum return a clear error explaining why Cloud runtime is not supported.
Why this matters:
  • IACMTerraformPlugin already works on Cloud runtime — there's no reason the Ansible plugin shouldn't have parity.
  • Many demo and dev environments have publicly reachable hosts. Requiring a persistent K8s delegate just to run Ansible adds infrastructure cost and complexity that isn't necessary when targets are reachable over the internet.
  • The current workaround (Run steps with shell-scripted ansible) works but bypasses the native IaCM Ansible integration — no registered playbooks, no registered inventories, no visibility in the Harness UI.
Reproduction steps:
  1. Create an IACM workspace with a registered playbook and inventory
  2. Create a pipeline with an IACM stage using Cloud runtime
  3. Add an IACMAnsiblePlugin step with command: run
  4. Execute — fails with exit status 1, no logs
Environment: Harness SaaS, IaCM module, August 2026