Bug 1225166

Opening a new bug based on 1013348 (comment 13). Related to this:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Provisioning_Guide/index.html

-----
The ask is as follows:

"I am missing more detailed documentation regarding Puppet modules. 

So far, the documentation reads:

"The next step is to upload a Puppet Module to the Puppet Module repository. You can also use the forge.puppetlabs.com as the URL to mirror Puppet Forge locally. This means that all of the content from Puppet Forge will be available on your Satellite. However, this requires downloading over 2700 modules and can take considerable time, depending on available bandwidth. This example uses the motd module because it is simple, and has no dependencies on other modules.
⁠

Procedure 3.4. To Upload a Puppet Module to the Repository:

    Download the motd puppet module from https://forge.puppetlabs.com/jeffmccune/motd. The file that you download will have a .tar.gz extension.
    Click Content → Products and then click Custom Products in the Name field.
    On the Repositories tab, click Puppet Modules to modify the Puppet Modules repository.
    In the Upload Puppet Module section, click Browse, and navigate to the motd module that you downloaded.
    Click Upload. Satellite displays Content successfully uploaded after the upload completes successfully.
"

But it does not detail the creation of your own Puppet modules. If it's the Puppet Forge way that is the correct one, I would expect a link to their documentation regarding the matter. Maintaining a Puppet Forge module without the proper tooling is also difficult, so perhaps you should say something about that, if it's not covered by Puppet Forge."