feat(argocd-wait-sync): add opt-in resource-level health tracking - #334
Merged
Conversation
Adds resource-name/resource-kind/resource-namespace inputs so the action can wait on a specific resource in the app's tree instead of the app's aggregate health, for apps that manage multiple independently-owned resources (e.g. a shared/monorepo-style app with several Deployments). Defaults preserve existing behavior exactly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016sb2uMVCHMsoWxYaPLAA7A
JesperTerkelsen
approved these changes
Aug 28, 2026
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
2 participants
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
resource-name(+resource-kind, defaultDeployment, andresource-namespace) inputs toargocd-wait-sync.resource-nameis set, completion and fail-fast (Degraded/Missing) are judged on that specific resource in.status.resources[]instead of the app's aggregate.status.health— so an app that manages multiple independently-owned resources (e.g. a shared/monorepo-style app with several Deployments) won't falsely pass before your resource rolls out, or block forever because an unrelated resource in the same app is Degraded/Progressing.resource-name(default) is fully backwards compatible — identical behavior to before.test-local.shgains matching--resource-name/--resource-kind/--resource-namespaceflags. README and CLAUDE.md updated.Test plan
bash -nonwait-sync.shandtest-local.shaction.ymljqcheck confirming the resource filter picks the tracked resource's health (Healthy) independently of app aggregate health (Degradedfrom an unrelated resource)test-local.shagainst a real shared ArgoCD app with--resource-namebefore merging🤖 Generated with Claude Code
https://claude.ai/code/session_016sb2uMVCHMsoWxYaPLAA7A