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.

Currently hammer-import-config-file builds and uploads the converted cfg-files, with an option to say "do not upload". It is more useful to the Sat6 user, to have the created-puppet-module tree available, to be imported into Sat6 'correctly'.

Switch the default behavior to 'just generate'. Change the name of the switch from --generate-only to --upload-modules.

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.

This is actually not a good idea. Uploading compiled-puppet-modules is the Way It's Done for Sat6. Sat5 customers using cfg-files are not generally puppet-savvy. the default should be "do it for them" - they can choose to not-upload when/if/as they become more adept at puppet-world.

Closing.