Skip to content

Conversation

downfa11
Copy link
Contributor

@downfa11 downfa11 commented Sep 4, 2025

Fixes[#24328]

  • cmd/util/app.go : options like --auto-prune are allowed to cases where auto-sync is disabled.
  • cmd/util/app_test.go : a test added to validate the updated option.
  • cmd/util/app.go, docs/user-guide/commands/* : examples like 'when sync is automated' updated.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@downfa11 downfa11 requested review from a team as code owners September 4, 2025 05:42
Copy link

bunnyshell bot commented Sep 4, 2025

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔵 /bns:start to start the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

Copy link

codecov bot commented Sep 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.37%. Comparing base (6f6c39d) to head (31eed5d).
⚠️ Report is 40 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #24380      +/-   ##
==========================================
+ Coverage   60.29%   60.37%   +0.07%     
==========================================
  Files         350      350              
  Lines       59959    60038      +79     
==========================================
+ Hits        36155    36247      +92     
+ Misses      20909    20881      -28     
- Partials     2895     2910      +15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

f.spec.SyncPolicy = nil
require.NoError(t, f.SetFlag("auto-prune", "true"))
require.NotNil(t, f.spec.SyncPolicy)
require.NotNil(t, f.spec.SyncPolicy.Automated)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing an assert to validate that spec.SyncPolicy.Automated.Enabled is false`.

  • It should be validated that if enabled: true (or not nil), then setting the flag will keep enabled to true.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the current app_test.go, the logic causes one test to affect another.

I added a Reset() method to prevent them from interfering with one another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants