Non Default Project
argocd.non-default-project
Requires Applications to belong to a named AppProject rather than the
permissive built-in default project, and (optionally) to a project on
an allow-list. Scoped AppProjects bound what an Application may deploy and
where — an ArgoCD-specific tenancy boundary.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Non Default Project with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/argocd@v1.0.5
include: [non-default-project]
# with: ...How This Guardrail Works
This guardrail is part of the ArgoCD Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|---|---|---|
allowed_projects
|
Required | — | Comma-separated allow-list of AppProject names for non-default-project. Empty means only enforce that the project is not `default`. |
ArgoCD Guardrails
This guardrail is part of the ArgoCD Guardrails policy, which includes 2 guardrails for deployment and infrastructure.
Ready to Automate Your Standards?
See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 200+ built-in guardrails.
AI agent rules & prompt files
Post-mortem action items
Security & compliance policies
Testing & quality requirements