Skip to content

[Automated] Update vault CLI Options#2638

Merged
thomhurst merged 1 commit into
mainfrom
automated/update-cli-options-vault
May 17, 2026
Merged

[Automated] Update vault CLI Options#2638
thomhurst merged 1 commit into
mainfrom
automated/update-cli-options-vault

Conversation

@thomhurst
Copy link
Copy Markdown
Owner

Summary

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

@thomhurst thomhurst added automated dependencies Pull requests that update a dependency file labels May 17, 2026
@thomhurst thomhurst enabled auto-merge (squash) May 17, 2026 03:20
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This automated PR updates only the generation timestamp in src/ModularPipelines.Vault/AssemblyInfo.Generated.cs — no actual Vault CLI options classes changed.

What Changed

The GeneratedAt assembly metadata attribute was bumped from 2026-05-10T03:18:25Z to 2026-05-17T03:19:27Z. This indicates the options generator ran against the installed Vault CLI and found no substantive changes to the command surface.

Observations

The automation is working correctly. The generator ran, compared the scraped CLI output against the existing generated code, found no differences in commands/options, and produced only a timestamp bump — exactly the right behavior.

Worth considering: suppress no-op PRs. When the generator produces no meaningful diff (only a timestamp change), it still opens a PR. This creates noise without any actionable review content. An improvement would be to add a pre-check in the generator workflow: if the only diff is the GeneratedAt timestamp, skip creating the PR altogether (or close it automatically). This keeps the PR backlog cleaner and makes automation-opened PRs more signal-rich for reviewers.

Auto-merge is appropriate here — even if the above suggestion were adopted, this particular PR is safe to merge as-is.

Verdict

No issues with the change itself. The one architectural suggestion above (suppress timestamp-only PRs) is worth filing as a future improvement to the generator workflow, but it's not a blocker for this PR.

@codacy-production
Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric Results
Complexity 0 (≤ 20 complexity)

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@thomhurst thomhurst merged commit 55de591 into main May 17, 2026
11 of 12 checks passed
@thomhurst thomhurst deleted the automated/update-cli-options-vault branch May 17, 2026 03:33
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