A file that belongs to a content unit.


A pluggable content protection mechanism that can be added to a Distribution, and is used exclusively by the content app to only had out binary data to trusted clients. “Trusted users” are defined by the type of ContentGuard used.

content unit

Content are the smallest units of data that can be added and removed from repositories. When singular, “content unit” should be used. Each content unit can have multiple artifacts. Each content unit has a type (like .rpm or .deb) which that is defined by a plugin.

content app

An aiohttp.server app provided by pulpcore that serves content through Distributions.


User facing object that configures the content app to serve either a Repository Version, a Repository, or a publications.


Push a Repository Version, a Repository, or a publications content to a remote location.

on-demand content

A content unit that was synchronized into Pulp but is missing one or more Artifacts. On-demand content is associated with a Remote that knows how to download those Artifacts.


A Django app that exends pulpcore to manage one or more types of content.


The metadata and artifacts of the content units in a repository version. Publications are served by the content app when they are assigned to a distribution.


A python package offering users a REST API and plugin writers a Plugin API. It is plugin based and manages content.


Stands for “Pulp Update Proposal”, and are the documents that specify process changes for the Pulp project and community.


User facing settings that specify how Pulp should interact with an external content source.


A versioned set of content units.


An immutable snapshot of the set of content units that are in a repository.


A plugin defined task that fetches content from an external source using a remote. The task adds and/or removes the content units to a repository, creating a new repository version.


Each content unit has a type (ex. rpm or docker) which is defined by a Plugin.