[Automated] Update podman CLI Options - #3970
Conversation
|
Warning Review limit reached
Next review available in: 34 minutes Limit details: You’ve used all 3 included reviews currently available under your plan. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (87)
📒 Files selected for processing (1)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8ef7582bcc
ℹ️ 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".
| /// The [KUBEFILE [KUBEFILE...]] operand. | ||
| /// </summary> | ||
| [CliArgument(0, Phase = CommandLinePhase.Passthrough)] | ||
| public string? KubefileKubefile { get; set; } |
There was a problem hiding this comment.
Model all kube files as a collection
The scraped synopsis explicitly allows [KUBEFILE [KUBEFILE...]], but this property can render only one string argument, so callers cannot use the new multi-file form of podman kube down; putting multiple paths in the string renders them as one quoted operand. PodmanKubePlayOptions.KubefileKubefile has the same defect, so both operands should be generated as nullable collections. Update the generator and regenerate these files rather than editing them directly.
AGENTS.md reference: AGENTS.md:L164-L169
Useful? React with 👍 / 👎.
| public record PodmanArtifactRmOptions( | ||
| [property: CliArgument(0, Phase = CommandLinePhase.Passthrough, Required = true)] IEnumerable<string> Artifact | ||
| ) : PodmanOptions |
There was a problem hiding this comment.
Allow all-removal without a required operand
When a caller wants All = true, this constructor still requires at least one artifact, and passing an empty collection does not work because CommandArgumentBuilder.AddArguments rejects empty values marked Required before Podman is invoked (src/ModularPipelines/Helpers/Internal/CommandArgumentBuilder.cs:159-163). Consequently the generated API cannot express the documented operand-free podman artifact rm --all command; PodmanQuadletRmOptions repeats the same conflict for quadlet rm --all. Correct the generator so these operands are optional and regenerate the files.
AGENTS.md reference: AGENTS.md:L164-L169
Useful? React with 👍 / 👎.
Review: [Automated] Update podman CLI Options (#3970)This is an auto-generated PR from
|
Summary
This PR contains automatically generated updates to podman CLI options classes.
The generator scraped the latest CLI help output from the installed tool.
Changes
Command coverage
Command coverage report:
Verification
🤖 Generated with ModularPipelines.OptionsGenerator