[Automated] Update pulumi CLI Options

[thomhurst]

Summary

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

Affected API families: Pulumi.

• Added APIs: 17
• Removed or changed APIs: 17
• Members with matching names but changed signatures: 0

Breaking changes are present. Consumers may need to update method arguments, option property types or nullability, enum members, and references to removed APIs.

Representative removed or changed members:

• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.AzureNative = 2 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.Gcp = 1 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.Kubernetes = 4 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.Oci = 3 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewScanSchedule.Daily = 2 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewScanSchedule

Representative added members:

• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.AzureNative = 1 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.Gcp = 2 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.Kubernetes = 3 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider.Oci = 4 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewProvider
• ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewScanSchedule.Daily = 1 -> ModularPipelines.Pulumi.Enums.PulumiInsightsAccountNewScanSchedule

Command coverage

Command coverage report:

• pulumi (v3.261.0): 233 commands, tree 26a5eadd276eea43631e4ac3298884c71fca0ef0efa6ed2e1270e406b45179b8
  • Baseline comparison: 233 commands at v3.261.0 -> 233 commands at v3.261.0

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

Summary by CodeRabbit

• New Features

  • Added support for executing Pulumi actions, configuring the Pulumi environment, and retrieving or promoting stack state.

• Breaking Changes

  • Several Pulumi configuration options, service operations, and scheduling choices are no longer available.
  • Supported provider, audit-log format, usage granularity, and stack scheduling selections have been reduced.
  • Pulumi service integrations now use updated command-context and result handling.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 07966b99-1446-4964-918a-88f9e6bcfa57

📥 Commits

Reviewing files that changed from the base of the PR and between 479e0f2 and ecafef7.

⛔ Files ignored due to path filters (8)

• src/ModularPipelines.Pulumi/Enums/PulumiInsightsAccountNewProvider.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Enums/PulumiInsightsAccountNewScanSchedule.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Enums/PulumiOrgAuditLogExportFormat.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Enums/PulumiOrgUsageGetGranularity.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Enums/PulumiStackScheduleEditOperation.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Enums/PulumiStackScheduleNewKind.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Enums/PulumiStackScheduleNewOperation.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Pulumi/Generated/Pulumi.Generation.json is excluded by !**/generated/**

📒 Files selected for processing (2)

• src/ModularPipelines.Pulumi/PublicAPI.Shipped.txt
• src/ModularPipelines.Pulumi/PublicAPI.Unshipped.txt

💤 Files with no reviewable changes (1)

• src/ModularPipelines.Pulumi/PublicAPI.Shipped.txt

Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The Pulumi public API baselines update enum values and remove obsolete enum members across Insights, organization, usage, and stack-schedule APIs.

Changes

Pulumi API baselines

Layer / File(s)	Summary
Regenerated enum values src/ModularPipelines.Pulumi/PublicAPI.Unshipped.txt	The unshipped baseline records revised numeric assignments for Pulumi enum members.
Shipped enum member removals src/ModularPipelines.Pulumi/PublicAPI.Shipped.txt	The shipped baseline removes obsolete members from Pulumi Insights, organization, usage, and stack-schedule enums.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to ecafe

This updates generated Pulumi CLI API baselines for the newer CLI output. The documented enum ordinal and API-surface breaking changes are intentional, with no remaining merge-readiness risk identified.

Poem

A rabbit checks each enum line
Values hop into a neat design
Old members rest beneath the tree
New baselines match precisely
The Pulumi trail is clean and bright

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies an automated update to the Pulumi CLI option classes, which is the main purpose of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch automated/update-cli-options-pulumi

---

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.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-07T15:54:31.785541Z	ecafef7	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cdc5c710ed

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

Review: PR #4736 — Pulumi enum options regeneration

This PR is a fully auto-generated update to the Pulumi CLI options package, touching only:

• 7 generated enum files (PulumiInsightsAccountNewProvider, PulumiInsightsAccountNewScanSchedule, PulumiOrgAuditLogExportFormat, PulumiOrgUsageGetGranularity, PulumiStackScheduleEditOperation, PulumiStackScheduleNewKind, PulumiStackScheduleNewOperation) — member reordering only
• Pulumi.Generation.json (source hash bump)
• PublicAPI.Shipped.txt / PublicAPI.Unshipped.txt (Roslyn public API tracking)

No hand-written code, generator source, or scraper logic was touched, so the "never hand-tweak generated options" and "fix in the scraper/generator" rules from CLAUDE.md don't come into play here — this is the generator's own output.

Verification performed:

• Confirmed the new enum member order is alphabetical by the [EnumValue] string across all 7 enums, consistently applied.
• Cross-checked PublicAPI.Shipped.txt/Unshipped.txt: every member whose ordinal changed is correctly removed from Shipped.txt and re-added (with *REMOVED* + new value) in Unshipped.txt; members whose ordinal happened not to change were correctly left alone.
• Confirmed none of these 7 enums are referenced elsewhere in src/ or test/ outside the generated files, so there's no ordinal-dependent call site in this repo.
• Confirmed (src/ModularPipelines/Helpers/Internal/CommandArgumentBuilder.cs:685) that CLI argument construction resolves enum values via the [EnumValue] attribute through reflection, not the underlying ordinal — so this reorder has no effect on runtime CLI behavior. The only theoretical exposure is external consumers who persisted/serialized the raw numeric enum value, which is expected, accepted fallout per CLAUDE.md's "current tool output is the sole source of truth" policy.

No prior substantive review comments exist on this PR to reconcile against (only a rate-limited CodeRabbit notice).

Verdict: No correctness bugs, no reuse/simplification/efficiency issues, and no CLAUDE.md violations. This is a clean, mechanical, low-risk regeneration.

[thomhurst]

Latest-options audit: this is the intentional one-time enum reorder from #4661 / merged #4663. That decision explicitly accepts the v4 ordinal break and prohibits restoring prior-output preservation. Named members still map through their unchanged EnumValue attributes; numeric/default consumers must account for the documented breaking change. No handwritten ordinal assignments or compatibility shims will be added. Resolving this review concern under the accepted generator policy.

[github-actions]

Code review

This is an automated ModularPipelines.OptionsGenerator update to the Pulumi enum options, picking up upstream CLI help changes for v3.261.0. I reviewed the full diff.

What changed:

• Several enums (PulumiInsightsAccountNewProvider, PulumiInsightsAccountNewScanSchedule, PulumiOrgAuditLogExportFormat, PulumiOrgUsageGetGranularity, PulumiStackScheduleEditOperation, PulumiStackScheduleNewKind, PulumiStackScheduleNewOperation) have their members re-sorted alphabetically by the generator, which shifts the underlying numeric enum values.
• Generated/Pulumi.Generation.json bumps the recorded generator source hash.
• PublicAPI.Shipped.txt and PublicAPI.Unshipped.txt are updated consistently with the enum changes (old numeric-valued members marked REMOVED, new ones added with their updated values), matching the Roslyn public-API-analyzer convention for pre-release breaking changes.

Assessment:

• All changed files are generated (Generated.cs sources, the generation manifest, and the PublicAPI tracking files) — no hand-edits to generated output, consistent with the repo rule to fix generator/scraper issues rather than touching generated files directly.
• The reordering is uniformly alphabetical across every touched enum, so this is a deterministic, mechanical generator output change rather than an ad-hoc or buggy edit.
• The resulting numeric-value changes to enum members are a real breaking change for anyone persisting/serializing these enums by underlying int, but per this repo policy, current tool output is treated as the source of truth even when regeneration causes breaking changes — and the PR description already documents the added/removed API surface accurately.

No issues found. Checked for correctness of the generated changes and CLAUDE.md compliance.

[github-actions]

Reviewed this automated Pulumi options regeneration PR.

The entire diff is mechanical: enum members are being reordered from CLI-declaration order to alphabetical order (by their [EnumValue] string), which shifts the underlying int values for several Pulumi* enums, and PublicAPI.Shipped.txt/PublicAPI.Unshipped.txt are updated accordingly (*REMOVED* + re-added entries). This matches existing generator behavior — CliEnumDefinition.cs:34 already sorts enum values via .OrderBy(value => value.CliValue, StringComparer.OrdinalIgnoreCase) — so this isn't a new/surprising change introduced by this PR, just a regeneration picking up a generator source change (generatorSourceSha256 bump in Pulumi.Generation.json) or a scrape where ordering previously differed.

Everything checked out:

• No hand-edited generated files — changes are confined to *.Generated.cs, Pulumi.Generation.json, and the PublicAPI.*.txt tracking files, consistent with this repo's rule that generated output is authoritative and not to be hand-patched.
• The PublicAPI.Unshipped.txt additions/removals are internally consistent with the enum diffs (same members, same reassigned ordinals).
• Per CLAUDE.md, breaking changes from regeneration are expected/accepted here rather than papered over with shims — none were added, correctly.
• PR description confirms the solution builds successfully.

No actionable findings.