[Automated] Update packer CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to packer 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

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• packer (Packer v1.16.0): 10 commands, tree be2df7c68caac570b0c20475b96703fc7102b079dafc1108b0b0e8f5b676a78e
  • Baseline comparison: 10 commands at Packer v1.16.0 -> 10 commands at Packer v1.16.0

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• src/ModularPipelines.Packer/Generated/Packer.Generation.json is excluded by !**/generated/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 68ea399c-07d0-4503-8e25-9589dbf6f536

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Review

This PR is a fully automated, mechanical update from the CLI options generator. The entire diff is a single-line change to src/ModularPipelines.Packer/Generated/Packer.Generation.json, updating generatorSourceSha256. No generated options classes, command coverage manifests, or public APIs changed — toolVersion (Packer v1.16.0) and commandTreeSha256 are unchanged, and the command coverage report confirms 10 commands before and after with no active public API impact.

Per scripts/Assert-GeneratedOptionsFreshness.ps1 / Write-GeneratedOptionsProvenance.ps1, generatorSourceSha256 is a fingerprint of the generator's own source inputs (not the scraped CLI output), used to detect when generated snapshots are stale relative to the generator on main. This PR simply re-stamps that fingerprint to match current main, which is exactly the expected/benign outcome when the generator source changes elsewhere but re-running produces identical output for this tool.

No prior review comments exist on this PR to reconcile (only an automated CodeRabbit "review skipped due to path filters" notice, which is expected since generated files are excluded from its review).

Assessment: No design, architectural, or correctness concerns — this is provenance bookkeeping working as intended, not a functional change. Nothing to suggest here.

[github-actions]

Review

This PR is a fully automated, mechanical update from the CLI options generator. The entire diff is a single-line change to src/ModularPipelines.Packer/Generated/Packer.Generation.json, bumping generatorSourceSha256. toolVersion (Packer v1.16.0) and commandTreeSha256 are unchanged, and the command coverage report confirms 10 commands before and after with no active public API impact — no generated options classes changed.

generatorSourceSha256 fingerprints the generator's own source inputs (not the scraped CLI output), used to detect when a tool's generated snapshot is stale relative to the generator on main. This PR simply re-stamps that fingerprint to match current main, which is the expected/benign outcome when the generator source changes elsewhere but re-running produces identical output for this tool.

No prior actionable review comments exist to reconcile — only an automated CodeRabbit "review skipped due to path filters" notice (expected, since generated files are excluded from its review) and an earlier automated review of a prior head that reached the same conclusion. The PR head has since moved but the change is the same trivial provenance bump.

Assessment: No design, architectural, or correctness concerns — this is provenance bookkeeping working as intended, not a functional change. Nothing to suggest here.