Bug #30004: As a user, i can import a content view version export into an existing content view - Katello - Foreman

Bug #30004

As a user, i can import a content view version export into an existing content view

Added by Partha Aji about 2 years ago. Updated almost 2 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Partha Aji

Category:

Inter Server Sync

Target version:

Katello 3.17.0

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

https://github.com/Katello/katello/pull/8932

Fixed in Releases:

Katello 4.0.0

Found in Releases:

Red Hat JIRA:

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)

Related issues

Associated revisions

Revision dce578c1 (diff)
Added by Partha Aji almost 2 years ago

Fixes #30004 - Api endpoint to import an exported content (#8932)

Fixes #30004 - Api endpoint to import an exported content

This commit allows you to import an exported content view dump via api.

Changes include
1) Adding a end point in CVV Controller that accepts cotent view and
import path
2) Modifying the publish action to handle import case.
3) Making the publish do the import instead of copy contents if
import_only is true.
4) Actions to orchestrate the importing
5) Actions to finally update the library instance with published
content.

History

#1 Updated by Partha Aji about 2 years ago

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)