[Automated] Update terraform CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to terraform CLI options classes.

The generator scraped the latest CLI help output from the installed tool.

Changes

• Updated options classes to reflect latest CLI documentation
• Added new commands if any were detected
• Updated option types and descriptions

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[claude]

Code Review

Summary

This is an automated PR that updates the Terraform CLI options generator timestamp in AssemblyInfo.Generated.cs. The single-line change bumps the ModularPipelines.OptionsGenerator.GeneratedAt metadata from 2026-02-15T03:12:18Z to 2026-03-01T03:12:29Z.

---

Observations

No actual option changes detected. The diff contains only the timestamp update — no new commands, no modified option types, no added/removed fields. The PR description says "Added new commands if any were detected" and "Updated option types and descriptions", but the change is purely a timestamp bump, suggesting the terraform CLI version scraped in this run produced identical options to the previous run.

This is expected and correct behaviour. The generator re-runs on a schedule to detect drift; when nothing changes in the CLI surface, only the "last checked" timestamp advances. This gives operators a clear audit trail of when the tool surface was last verified, without introducing unnecessary noise in the options classes.

No issues found. The pattern is clean, the generated file is appropriately excluded from code coverage (per the project conventions), and the change is minimal and safe to merge.

---

Minor Architectural Note (non-blocking)

If the intent of scheduling automated regeneration is purely to catch CLI drift, it may be worth considering whether committing a timestamp-only diff adds useful signal or just generates PR noise. One alternative would be to only open/update the PR when substantive option changes are detected, and skip the PR entirely on no-op runs. That said, the current approach does provide a visible "health check" that the generator ran successfully, which has its own value — so this is a judgement call, not a defect.

---

Verdict: LGTM. Safe to merge.