Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
pulp-puppet-module-builder can be used to prepare a synchronizable repository of Puppet content, but it requires operating on module "source."

Since, for example, Puppet Forge provides modules as tar files, it would be nice if you could run pulp-puppet-module-builder against a folder full of tar files directly.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Created attachment 916155 [details]
manifest builder

This is a simple bash script that will make a PULP_MANIFEST out of any files you give it. There is a lot of value in having this be separate from pulp_puppet_module_builder, since users may need to make a manifest file from other file types (such as isos).

Can you confirm the files contain built puppet modules.  Or, do they contain module source?

My reading is that this refers to a directory of built puppet modules, in tar form as they come from puppet forge.

Since they are already built, there is nothing for pulp-puppet-module-builder to do, so I am closing this. Please re-open if there is a change you think we should make.

The Pulp upstream bug status is at CLOSED - NOTABUG. Updating the external tracker on this bug.

Not sure why closed bugs still bug me about needinfo.