Skip to content

[Automated] Update packer CLI Options - #4762

Open
thomhurst wants to merge 1 commit into
mainfrom
automated/update-cli-options-packer
Open

[Automated] Update packer CLI Options#4762
thomhurst wants to merge 1 commit into
mainfrom
automated/update-cli-options-packer

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

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

@thomhurst thomhurst added automated dependencies Pull requests that update a dependency file labels Sep 6, 2026
@coderabbitai

coderabbitai Bot commented Sep 6, 2026

Copy link
Copy Markdown

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: 4936feb1-25ac-4784-bfc9-6b4e23919542

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

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

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Code review

This PR is an automated, generator-produced update to src/ModularPipelines.Packer/Generated/Packer.Generation.json. The only change is the generatorSourceSha256 value (recording that the generator source changed), with no command-tree or option-shape differences — Packer stays at 10 commands / same tree hash. This is exactly the kind of trivial, auto-generated, obviously-correct change described in the repo's CLAUDE.md as not needing hand-editing (generated files are the source of truth and shouldn't be hand-tweaked in a PR).

No issues found. Checked for bugs and CLAUDE.md compliance.

@thomhurst
thomhurst force-pushed the automated/update-cli-options-packer branch from 08ce688 to f2a7b29 Compare September 7, 2026 15:52
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Code review

This PR is a fully automated, generator-produced regeneration of src/ModularPipelines.Packer/Generated/Packer.Generation.json. The diff is a single line:

-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "4f583590c7bc1fb5c9bd0360c7986f13acb231fe933e1989457e137aa1339444"

generatorSourceSha256 is a fingerprint of the generator's own source (per GeneratedOptionsProvenance.ps1), used only to detect staleness of the generated snapshot versus the current generator code — it does not affect Packer's CLI surface. toolName, toolVersion, and commandTreeSha256 are all unchanged, meaning Packer's command tree and generated option classes are unaffected by this update. No generated C# files were hand-edited, consistent with CLAUDE.md's guidance that generated output is authoritative and must not be hand-tweaked.

I compared this against the prior review on this PR (CLEAR, posted at an earlier head SHA): the underlying diff is identical — only a rebase moved the head SHA — so nothing new to flag.

No issues found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant