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
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
Bin,
Which plugin are you referring to? Some plugins have metadata and therefore
require publications (pulp_file, pulp_rpm, etc) while others such as
pulp_ansible have live APIs and therefore do not require publications.
For plugins without publications, it's possible to set repository or
Theoretically you should be able to use pulpcore-client even with LDAP
authentication in the web server. However, I have not tested this. I've
only helped users that use certificate authentication in the webserver.
What error are you seeing on the client side? Do you see any errors in pulp
logs?
Thanks Dennis.
We use pulpcore python client to interact with api. Once we enable ldap on
nginx, the below code that pulpcore-client authenticate will not work any more.
I am wonder if we are still be able to use pulpcore-client? or we have to
rewrite the client code. This sounds too much
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
