Description of problem:

As described in https://bugzilla.redhat.com/show_bug.cgi?id=2277970 and also mentioned in https://github.com/theforeman/foreman-ansible-modules/issues/1717

There are two types of export formats present i.e. importable and syncable

To import an "importable" export, That export data needs to have valid metadata generated as well.

To import a "syncable" export, That export data needs to have a valid metadata as well as listing files generated.

But when an end-user is trying to automate the process of export and import using the Rest API or the redhat.satellite.content_export_* modules, They generate an export data that is missing either just the metadata.json or both the metadata.json and the listing files.

And that calls for additional arrangements to ensure that the user have executed "hammer content-export generate-metadata" and "hammer content-export generate-listing" commands against the right exports.

Version-Release number of selected component (if applicable):

Supported version of Red Hat Satellite 6 [ tested on Satellite 6.14.3 ]

How reproducible:

Always and easily

Steps to Reproduce:
1. Set up a satellite with few repos synced in immediate mode
2. Try doing a syncable and importable type complete export of the Library environment using redhat.satellite.content_export_library ansible module
3. check the contents of export directory

Actual results:

No metadata.json present for importable export content
No metadata.json + listing files present for syncable export content

Expected results:

The export modules should have the ability to trigger the required metadata\listing file generations
or
A separate module should be developed to do the same task and referred in the redhat.satellite.content_export_* modules
or
An alternate solution needs to be documented in the examples of redhat.satellite.content_export_* modules

Additional info:

NA