Bug #30004
closed
As a user, i can import a content view version export into an existing content view
Added by Partha Aji over 4 years ago.
Updated about 4 years ago.
Category:
Inter Server Sync
|
Description
As a user, i can import a content view version export into an existing content view
hammer content-view version import --organization=org --name=foo --metadata=<metadata file>
Precheck
- Metadata + Dump should exist (checks for checksums)
- Content View must exist
- ‘Shell’ library repositories of the repositories in the content view must exist
- We can try automating this as extra credit
- As a user I can import the import file and the repositories and content views would be created for me if not present.
Add an “import” functionality that
- Creates a new version
- Create a new repository in pulp (if not already created)
- Configure a pulp importer, give it a repo mapping and the location of the dump.
- Call the pulp import api
- Tackle other operations similar to CV publish.
- Copy over the deltas between cv version repo and library repo (due to applicability calculations)
As a user, i can import a content view version export into an existing content view
hammer content-view version import --organization=org --name=foo --metadata=<metadata file>
Precheck
- Metadata + Dump should exist (checks for checksums)
- Content View must exist
- ‘Shell’ library repositories of the repositories in the content view must exist
- We can try automating this as extra credit
- As a user I can import the import file and the repositories and content views would be created for me if not present.
Add an “import” functionality that
- Creates a new version
- Create a new repository in pulp (if not already created)
- Configure a pulp importer, give it a repo mapping and the location of the dump.
- Call the pulp import api
- Tackle other operations similar to CV publish.
- Copy over the deltas between cv version repo and library repo (due to applicability calculations)
- Also i can import a Composite content view version export into an existing content view
- Call out to the docs team
- Category set to Inter Server Sync
- Target version set to Katello 4.0.0
- Triaged changed from No to Yes
- Target version changed from Katello 4.0.0 to Katello 3.17.0
- Status changed from New to Ready For Testing
- Assignee set to Partha Aji
- Pull request https://github.com/Katello/katello/pull/8932 added
- Fixed in Releases Katello 4.0.0 added
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF