[Automated] Update argocd CLI Options - #4607
Open
thomhurst wants to merge 1 commit into
Open
Conversation
thomhurst
added
automated
dependencies
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. 💤 Files selected but had no reviewable changes (2)
⛔ Files ignored due to path filters (199)
⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (199)
📒 Files selected for processing (2)
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
Owner
Author
|
Base branch advanced from |
Owner
Author
Owner
Author
thomhurst
force-pushed
the
automated/update-cli-options-argocd
branch
from
September 6, 2026 07:59
c219fd4 to
c58f8ca
Compare
|
Too many files changed for review (201 files, 100 file limit). Bypass the limit by tagging |
thomhurst
temporarily deployed
to
Pull Requests
September 6, 2026 08:10 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
ReviewThis PR is the automated ArgoCd CLI options regeneration. I compared the generation metadata and generated output between the base branch and PR head. Blocking: generator regression silently reassigns enum ordinal values
Despite the CLI output being identical, every generated enum in the package has been alphabetically resorted, which silently reassigns the underlying numeric value of every non-explicitly-numbered member. For example, Debug,
-Info,
-Warn,
-Error
+Error,
+Info,
+Warn
Why this matters: any consumer who serializes, persists, compares, or casts these enums by numeric value (stored config, cached pipeline state, Suggested fix: the generator should preserve the CLI's declared member order (i.e., the order options/values are scraped from I didn't find any other issues in this generated diff — file naming, attribute usage, and command coverage all look consistent with the existing generator conventions, and the rest of the reordering is an artifact of the same root cause above. |
thomhurst
force-pushed
the
automated/update-cli-options-argocd
branch
from
September 6, 2026 08:51
c58f8ca to
b47742d
Compare
Contributor
Code reviewThis PR is a fully auto-generated update from
Per No issues found. Checked for correctness of the generated output and CLAUDE.md compliance. |
thomhurst
enabled auto-merge (squash)
September 6, 2026 09:51
thomhurst
had a problem deploying
to
Pull Requests
September 6, 2026 10:01 — with
GitHub Actions
Error
GitHub Actions
Error
thomhurst
disabled auto-merge
September 6, 2026 14:19
thomhurst
force-pushed
the
automated/update-cli-options-argocd
branch
from
September 6, 2026 14:21
b47742d to
ff07ea4
Compare
Contributor
Code reviewThis PR is a fully auto-generated regeneration of the Scope check: every changed file is Resolving the earlier "Blocking" finding on enum reordering: A previous review correctly observed that Other observations (non-blocking):
No actionable issues found in this PR's own diff. |
thomhurst
force-pushed
the
automated/update-cli-options-argocd
branch
from
September 7, 2026 15:50
ff07ea4 to
0ca42cd
Compare
Contributor
Code reviewThis PR is a fully auto-generated regeneration of the Scope check: all 201 changed files are Re-verifying the previously-resolved enum-reordering concern: Other observations (non-blocking):
No actionable issues found in this PR's own diff. |
thomhurst
force-pushed
the
automated/update-cli-options-argocd
branch
from
September 8, 2026 09:57
0ca42cd to
18bc8cc
Compare
Contributor
Code reviewThis is another automated regeneration of the Scope check: all 201 changed files are still What changed since the last-reviewed head: Other observations (non-blocking): the one non-mechanical content change is still the newly-scraped Per |
thomhurst
force-pushed
the
automated/update-cli-options-argocd
branch
from
September 8, 2026 21:10
18bc8cc to
df97138
Compare
Contributor
Code reviewThis is another automated regeneration of the Scope check: all 201 changed files are Re-verified the enum-reordering root cause: Other observations (non-blocking):
No actionable issues found in this PR's own diff. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR contains automatically generated updates to argocd CLI options classes.
The generator scraped the latest CLI help output from the installed tool.
Changes
Assembly-wide public API impact
Affected API families:
ArgoCd.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.ArgoCd.Enums.ArgoCdAccountBcryptLoglevel.Error = 3 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevel.Info = 1 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevel.Warn = 2 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevel.Error = 3 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevel.Info = 1 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevelRepresentative added members:
ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevel.Error = 1 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevel.Info = 2 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevel.Warn = 3 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountBcryptLoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevel.Error = 1 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevelModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevel.Info = 2 -> ModularPipelines.ArgoCd.Enums.ArgoCdAccountCanILoglevelCommand coverage
Command coverage report:
Verification
🤖 Generated with ModularPipelines.OptionsGenerator