[Automated] Update vault CLI Options

[thomhurst]

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

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• vault (Vault v2.1.0 (cb6a54face072e372480d7cc2e64a3110b84756f), built 2026-08-31T13:29:27Z): 122 commands, tree f36ed874ca357f0eaaca930ad12a318f29c127df35a38f4096aae134e56ae477
  • Baseline comparison: 122 commands at Vault v2.1.0 (cb6a54face072e372480d7cc2e64a3110b84756f), built 2026-08-31T13:29:27Z -> 122 commands at Vault v2.1.0 (cb6a54face072e372480d7cc2e64a3110b84756f), built 2026-08-31T13:29:27Z

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.Vault/Generated/Vault.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: 0e4606cc-6a99-4cf1-9acf-7bd568fa6e40

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, bookkeeping-only regeneration of the Vault CLI options. The diff touches exactly one file:

--- a/src/ModularPipelines.Vault/Generated/Vault.Generation.json
+++ b/src/ModularPipelines.Vault/Generated/Vault.Generation.json
-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "bdf2981af64a9665cc6851ff1c5ed256989395d930ae8345ca28cd09d755e620"

• toolVersion and commandTreeSha256 are unchanged, so the Vault CLI's command surface did not change — only the hash tracking which generator source last produced the output was bumped.
• No generated options classes, no hand-written source, and no logic of any kind changed.
• Per repo convention, generated-options changes are driven by the scraper/generator, not hand-edited, and this file carries [ExcludeFromCodeCoverage] — consistent with an auto-generated, no-op-behavior update.

No actionable findings. Nothing here warrants a design or architecture suggestion since there's no logic to evaluate.

[github-actions]

Review

This PR is a fully automated, bookkeeping-only regeneration of the Vault CLI options. The diff touches exactly one file:

--- a/src/ModularPipelines.Vault/Generated/Vault.Generation.json
+++ b/src/ModularPipelines.Vault/Generated/Vault.Generation.json
-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "4f583590c7..."

• toolVersion and command coverage (122 → 122 commands, same tree hash) are unchanged, so the Vault CLI's command surface did not change — only the generatorSourceSha256 provenance hash was bumped.
• That hash is computed by scripts/GeneratedOptionsProvenance.ps1 from the git object IDs of the generator's source inputs, one of which is Directory.Packages.props. That file changed on main in the recent chore(deps): update tunit monorepo to 1.66.27 commit, which is why the fingerprint moved even though nothing Vault-specific changed.
• No generated options classes, no hand-written source, and no logic changed. Per repo convention, this generated file is authoritative and must not be hand-edited — there is nothing here to hand-edit anyway.
• A prior automated review on an earlier commit of this PR reached the same conclusion (no actionable findings); the PR was since updated with a newer hash value but the nature of the change is unchanged.

No actionable findings. Nothing here warrants a design or architecture suggestion since there's no logic to evaluate.