nasus20202/ArgoCD Build & Validate Manifests

Build Kubernetes manifests from ArgoCD application definitions and validate them using kubeconform

Trust Signals

workflow.ymlSHA-pinned

uses: nasus20202/argocd-validate-action@babf1e1b1b39f0087944930d91eccb12d43a54a6 # v3.1.4

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
manifests-dir	Directory to output generated manifests	no	manifests
apps-dir	Directory containing ArgoCD application manifests	yes	""
skip-files	Comma-separated list of files to skip	no	""
skip-resources	Comma-separated list of Kubernetes resources to skip during validation	no	CustomResourceDefinition
state-dir	Directory for storing manifest state for diff comparison. If empty or non-existent, it will be initialized with current manifests.	no	""
comment-on-pr	Whether to post manifest diff as a PR comment (requires state-dir to be set)	no	false
github-token	GitHub token for posting PR comments (defaults to github.token)	no	""
commit-state	Whether to commit the state directory back to the repository after comparison (e.g. after merging a PR). Requires github-token with write permissions.	no	false
validate-argo	Whether to validate ArgoCD application/applicationset definitions before rendering	no	true
kube-version	Kubernetes version to pass to helm template (e.g. 1.30.0). Auto-detected if not set.	no	""
schema-locations	Comma-separated additional kubeconform schema locations for CRD validation	no	""
verbose	Enable verbose debug output	no	false

name	description
diff-status	Diff status: 'initialized', 'changed', or 'unchanged'
diff-summary	One-line summary of changes (e.g. Added/Removed/Modified counts)
diff-comment-file	Path to generated PR comment markdown file (set when status is 'changed')