{{ 'New Repository' | translate }}

New Repository

Basic Information

Publishing Settings

The repository will only be available on content hosts with the selected architecture.

The repository will only be available on content hosts with the selected OS version.

Sync Settings

{{urlDescription}}

URL of the registry you want to sync. Example: https://registry-1.docker.io/ or https://quay.io/

Content synced depends on the specifity of the URL and/or the optional requirements.yaml specified below

URL to the repository base. Example: http://ftp.de.debian.org/debian/

Upload Requirements.yml file

Include dependencies of Ansible collections in the repository.

The URL to receive a session token from, e.g. used with Automation Hub.

The token key to use for authentication.

Whitespace-separated list of releases/distributions to sync (required for syncing). Example: buster


Warning. Are you sure you want to add a comma in this whitespace separated list of distributions?

Whitespace-separated list of components to sync (leave clear to sync all). Example: main


Warning. Are you sure you want to add a comma in this whitespace separated list of components?

Whitespace-separated list of processor architectures to sync (leave clear to sync all). Example: amd64


Warning. Are you sure you want to add a comma in this whitespace separated list of architectures?

Name of the upstream repository you want to sync. Example: 'quay/busybox' or 'fedora/ssh'.

Selecting this option will exclude SRPMs from repository synchronization.

Selecting this option will exclude treeinfo files from repository synchronization.
Select this option if treeinfo files or other kickstart content is failing to syncronize from the upstream repository.

Selecting this option will result in Katello verifying that the upstream url's SSL certificates are signed by a trusted CA. Unselect if you do not want this verification.

Username of the upstream repository user for authentication. Leave empty if repository does not require authentication.

Password of the upstream repository user for authentication. Leave empty if repository does not require authentication.

Token of the upstream repository user for authentication. Leave empty if repository does not require authentication.

{{option.description}}

{{option.description}}

{{option.description}}

For On Demand synchronization, only the metadata is downloaded during sync and packages are fetched and stored on the filesystem when clients request them. On Demand is not recommended for custom repositories unless the upstream repository maintains older versions of packages within the repository. The Immediate option will download all metadata and packages immediately during the sync.

  • Additive: new content available during sync will be added to the repository, and no content will be removed.
  • Mirror Content Only: any new content available during sync will be added to the repository and any content removed from the upstream repository will be removed from the local repository.
  • Mirror Complete: a sync behaves exactly like "Mirror Content Only", but also mirrors metadata as well. This is the fastest method, and preserves repository signatures, but is only supported by yum and not by all upstream repositories.

A comma-separated list of container image tags to include when syncing.

A comma-separated list of container image tags to exclude when syncing. Source images are excluded by default because they are often large and unwanted.

The maximum number of versions of each package to keep.

No HTTP Proxies found

Published Repository Information

Do not require a subscription entitlement certificate for accessing this repository.