From 7c45157a92f7bc02e4bd91c7af06dd404907cc29 Mon Sep 17 00:00:00 2001 From: Ken Dreyer Date: Wed, 2 Jan 2019 14:16:03 -0500 Subject: [PATCH] doc: describe product_id's output and purpose Document the "productid" files that Pungi creates when the user configures the "product_id" setting. Describe where to find the "productid" files, and how they relate to subscription-manager. Signed-off-by: Ken Dreyer --- doc/configuration.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/configuration.rst b/doc/configuration.rst index c9ac3dcb..a7f1d1a4 100644 --- a/doc/configuration.rst +++ b/doc/configuration.rst @@ -433,8 +433,13 @@ Options **product_id** = None (:ref:`scm_dict `) -- If specified, it should point to a - directory with certificates ``--*.pem``. This - certificate will be injected into the repository. + directory with certificates ``--*.pem``. Pungi will + copy each certificate file into the relevant Yum repositories as a + ``productid`` file in the ``repodata`` directories. The purpose of these + ``productid`` files is to expose the product data to `subscription-manager + `_. + subscription-manager inclues a "product-id" Yum plugin that can read these + ``productid`` certificate files from each Yum repository. **product_id_allow_missing** = False (*bool*) -- When ``product_id`` is used and a certificate for some variant