Also regarding the order of the creation of these things, I believe in all cases a Distribution (of any type) can be created before it's corresponding repository_version or in other cases a publication (depending on the content type's needs). The use case is that a user may want to design their Distribution base_path URL layout and receive sections of it even before they have content to serve from those Distributions.
On Fri, Apr 17, 2020 at 10:52 AM Dennis Kliban <[email protected]> wrote: > Some content types require publications and others don't. It all depends > on the requirements of the client that consumes content. For example, > yum/dnf expects to find metadata about all the packages in the repository. > Since a RepositoryVersion only contains the packages, you must create a > Publication to generate the metadata. On the other hand 'podman' and > 'docker' interact with a REST API that serves content without any special > metadata. So Container repositories and repository versions can be directly > associated with ContainerDistributions. > > On Fri, Apr 17, 2020 at 9:59 AM Bin Li (BLOOMBERG/ 120 PARK) < > [email protected]> wrote: > >> I was under impression that the publication has to be created before >> creating a distribution. It looks like now I can create a distribution by >> specify a repository or repository version. Is the publication created >> automatically in this case? If not, in what scenario we need a create a >> publication before create a distribution? >> >> Thanks >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
