Support threads -
Context
-------
We run Terraform via IaCM on GovCloud/FIPS Kubernetes workers (FIPS OpenSSH, e.g. platform validation nodepools). Pipelines use private Git module sources, e.g. git::git@git.autodesk.com:...
Problem
-------
IACMTerraformPlugin step "init" fails during module download (git clone/fetch). Typical error: "c25519 is not allowed in FIPS mode" (or similar FIPS/SSH KEX failures).
We set FIPS-related env on the IaCM init step (e.g. GIT_SSH_FIPS_KEX_ALGORITHMS, AWS_USE_FIPS_ENDPOINT). GIT_SSH_FIPS_* on IACMTerraformPlugin does not appear to reach the git subprocess the way it does in our working CD/cos-tf Plugin init path.
Initial test
------------
  • Failing path: IACMTerraformPlugin init with git::git@... modules on FIPS nodes.
  • Working path: Plugin (cos-tf) terraform init with DRONE_SSH_KEY, DRONE_NETRC_MACHINE, GIT_SSH_FIPS_KEX_ALGORITHMS, TF_CLI_ARGS_init=-backend=false (same module sources).
Root cause (observed)
---------------------
Parity gap: on FIPS OpenSSH, git must use FIPS-allowable KEX/host algorithms. cos-tf Plugin wires SSH/deploy key + FIPS KEX correctly; native IaCM init still invokes git with defaults that can pick curve25519.
Interim workaround (not acceptable long-term)
---------------------------------------------
Prefetch modules with Plugin init, then IACMTerraformPlugin init with TF_CLI_ARGS_init=-get=false, plus workspace permission fixes (root prefetch vs non-root IaCM). This is fragile (two-step init, cache drift, DRONE_* coupling, easy to miss in new pipelines).
Requested feature / fix
-----------------------
IACMTerraformPlugin init: apply FIPS-safe Git/SSH for all git subprocesses used for module download (honor GIT_SSH_FIPS_KEX_ALGORITHMS and/or documented equivalent; parity with CD Terraform Plugin / SSH modules).