Detect GitOps mode from ArgoCD Application YAML file#2
Open
nadaverell wants to merge 1 commit into
Open
Conversation
Check for deploy/argocd/{env}.yaml existence as the primary signal for
gitops mode, instead of grepping kustomize build output for the
managed-by label. Falls back to label check for backwards compatibility.
Includes diagnostic logging of the resolved path, explicit notice when
falling back to label detection, and proper error handling for kustomize
build failures in the fallback path.
nadaverell
force-pushed
the
fix/argocd-detection-from-yaml-file
branch
from
abc9b1d to
e71e7f4
Compare
arlenskh
approved these changes
Mar 19, 2026
4 tasks
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
deploy/argocd/{env}.yamlfile existence instead of grepping kustomize build output formanaged-bylabelExtractArgoCDConfig(ArgoCD YAML file existence) is the single source of truthContext
The
managed-by: argocdlabel in manifests could be missing (e.g. manually created services) even when ArgoCD was enabled, causing the action to silently fall back tokubectl applymode. The ArgoCD Application YAML file is the authoritative signal.Related