ApplicationSet SCM generators filter archived repositories

Introduced 2026-08-04 · score 0.98

HOW TO USE IT

When configuring an ApplicationSet SCM generator for GitHub or Gitea, set `excludeArchivedRepos: true` to exclude archived repositories; for GitLab, set `includeArchivedRepos: true` to include them. Both fields default to false.

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: <appset-name>
spec:
  generators:
    - scmProvider:
        github:
          organization: <github-organization>
          excludeArchivedRepos: true

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: <appset-name>
spec:
  generators:
    - scmProvider:
        gitlab:
          group: <gitlab-group-id-or-path>
          includeArchivedRepos: true

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: <appset-name>
spec:
  generators:
    - scmProvider:
        gitea:
          owner: <gitea-organization>
          excludeArchivedRepos: true

WHY THIS HELPS

Configure an ApplicationSet SCM generator to include or exclude archived repositories.

REQUIREMENTS AND LIMITATIONS

Version: v3.5.0
excludeArchivedRepos: Exclude archived repositories; defaults to false. Documented for GitHub and Gitea.
includeArchivedRepos: Include archived repositories; defaults to false. Documented for GitLab.
github.organization (required): Name of the GitHub organization to scan.
gitlab.group (required): Name of the base GitLab group to scan; may be a group ID or full namespaced path.
gitea.owner (required): Name of the Gitea organization to scan.
The filter currently supports GitHub, GitLab, and Gitea.
GitLab excludes archived repositories by default; its option allows archived repositories to be included.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

ApplicationSet SCM generators filter archived repositories