Skip to content

fix: trigger app sync on app-set spec change#26811

Open
ppapapetrou76 wants to merge 3 commits intoargoproj:masterfrom
ppapapetrou76:26585-trigger-app-sync-on-appset-spec-change
Open

fix: trigger app sync on app-set spec change#26811
ppapapetrou76 wants to merge 3 commits intoargoproj:masterfrom
ppapapetrou76:26585-trigger-app-sync-on-appset-spec-change

Conversation

@ppapapetrou76
Copy link
Contributor

@ppapapetrou76 ppapapetrou76 commented Mar 12, 2026

Closes #26585

Fixes the code top trigger applications sync when there's a change in the application set spec ( that apparantely generated the apps )

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

Signed-off-by: Patroklos Papapetrou <ppapapetrou76@gmail.com>
@bunnyshell
Copy link

bunnyshell bot commented Mar 12, 2026

🔴 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

@codecov
Copy link

codecov bot commented Mar 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.99%. Comparing base (3a4b0a0) to head (1f02681).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #26811   +/-   ##
=======================================
  Coverage   62.98%   62.99%           
=======================================
  Files         414      414           
  Lines       56153    56166   +13     
=======================================
+ Hits        35370    35382   +12     
  Misses      17416    17416           
- Partials     3367     3368    +1     

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

@ppapapetrou76 ppapapetrou76 marked this pull request as ready for review March 13, 2026 11:39
@ppapapetrou76 ppapapetrou76 requested a review from a team as a code owner March 13, 2026 11:39
Copy link
Member

@ishitasequeira ishitasequeira left a comment

Choose a reason for hiding this comment

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

Overall changes look good. Added a nit!!

Comment on lines +1205 to +1211
case revisionsChanged && specChanged:
newAppStatus.Message = "Application has pending changes (revision and spec differ), setting status to Waiting"
case revisionsChanged:
newAppStatus.Message = "Application has pending changes, setting status to Waiting"
default:
newAppStatus.Message = "Application has pending changes (spec differs), setting status to Waiting"
}
Copy link
Member

Choose a reason for hiding this comment

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

nit: we are adding what differs in each message except for revisionsChanged. Shall we align on the message?

Comment on lines +1204 to +1211
switch {
case revisionsChanged && specChanged:
newAppStatus.Message = "Application has pending changes (revision and spec differ), setting status to Waiting"
case revisionsChanged:
newAppStatus.Message = "Application has pending changes, setting status to Waiting"
default:
newAppStatus.Message = "Application has pending changes (spec differs), setting status to Waiting"
}
Copy link
Member

Choose a reason for hiding this comment

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

How about making messages const ? I think it's better to do it since we can use same const in logic and tests.

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.

Progressive sync out of sync when changing image sha

3 participants