feat: add a dry run option to the sync modal - #279
Conversation
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
🚥 Pre-merge checks | ✅ 5 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 10.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 10 functions across 8 files. (2 skipped: 2 unsupported.) 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 |
|
@coderabbitai review |
|
3942ddf to
6b858e6
Compare
|
@coderabbitai review |
|
6b858e6 to
f831dcb
Compare
e37f044 to
c8dc12b
Compare
f831dcb to
93890e9
Compare
dtoggles a dry run. Argo CD runs the same pre-flight it already gates every sync behind (kubectl apply --dry-runover all manifests), reports per-resource results, and applies nothing.Two interactions with force, both from the same fact — a client-side dry run never touches a live resource:
inert in dry runinstead of reddelete & recreateReads
Sync (dry run)in the pane afterwards, from #277.Stacked on #278.
Summary by CodeRabbit
dkey in the sync confirmation dialog.