allow import and export of composite content views
If you attempt to export a composite CV right now, it will export as a "regular" cv. This is incorrect.
Instead, it should export with the information needed to reconstitute the composite CV on the importing side. CV version import should be able to handle composite imports as well.
Previously, CV import/export would treat composites as "regular"
content views. This resulted in each repo of the composite being
exported as if it was part of a regular content view.
These exports were unable to be imported since the repos existed on
the components and not the composite.
This commit exports composite content views with information needed to
reconstitute them on the importing side. Each component CV name and
version is written to the JSON, and upon import, hammer searches for
the matching name and version on the importing side. If all of the
info lines up, the components are associated with the CV and a publish
#3 Updated by Chris Duryee about 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset hammer-cli-katello|db3146eaf327ab30038052a8d107768807b400d5.