Project

General

Profile

Actions

Feature #35948

closed

Need incremental export for syncable format

Added by Partha Aji over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Inter Server Sync
Target version:
Difficulty:
hard
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Description of problem:

As of today we only have support for complete exports in a syncable format. Need ability to incrementally export in the syncable format.

1. hammer content-export incremental <library, repository, version> -h

The --format option is not present.

Actual results:

Usage:
hammer content-export incremental version [OPTIONS]

Options:
--async Do not wait for the task
--chunk-size-gb NUMBER Split the exported content into archives no greater than the specified size in
gigabytes.
--content-view[-id] VALUE/NUMBER Name/Id of associated content view
--destination-server VALUE Destination Server name
--fail-on-missing-content Fails if any of the repositories belonging to this version are unexportable.
--from-history-id NUMBER Export history id used for incremental export. If not provided the most recent
export history will be used.
--id NUMBER Content view version id
--lifecycle-environment[-id] VALUE/NUMBER Name/Id of associated lifecycle environment
--organization[-id|-title|-label] VALUE/NUMBER Name/Title/Label/Id of associated organization
--version VALUE Filter versions by version number.
-h, --help Print help

Expected results:

Usage:
hammer content-export incremental version [OPTIONS]

Options:
--async Do not wait for the task
--chunk-size-gb NUMBER Split the exported content into archives no greater than the specified size in
gigabytes.
--content-view[-id] VALUE/NUMBER Name/Id of associated content view
--destination-server VALUE Destination Server name
--fail-on-missing-content Fails if any of the repositories belonging to this version are unexportable.
--format ENUM Export formats. Choose syncable if content is to be imported via repository
sync. Choose importable if content is to be imported via hammer content-import.

--from-history-id NUMBER                       Export history id used for incremental export. If not provided the most recent
export history will be used.
--id NUMBER Content view version id
--lifecycle-environment[-id] VALUE/NUMBER Name/Id of associated lifecycle environment
--organization[-id|-title|-label] VALUE/NUMBER Name/Title/Label/Id of associated organization
--version VALUE Filter versions by version number.
-h, --help Print help

Additional info:

Also, when a library export is performed, a sort of Content View is created...but it doesn't appear under the Content View list.

Actions #1

Updated by Partha Aji over 1 year ago

Also note this issue needs to resolved in parallel to https://github.com/pulp/pulpcore/pull/3511

Actions #2

Updated by Partha Aji over 1 year ago

  • Bugzilla link set to 2143497
Actions #3

Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Assignee set to Partha Aji
  • Pull request https://github.com/Katello/katello/pull/10417 added
Actions #4

Updated by Jeremy Lenz over 1 year ago

  • Target version set to Katello 4.8.0
  • Triaged changed from No to Yes
Actions #5

Updated by Jeremy Lenz over 1 year ago

  • Triaged changed from Yes to No
Actions #6

Updated by Chris Roberts over 1 year ago

  • Difficulty set to hard
  • Triaged changed from No to Yes
Actions #7

Updated by The Foreman Bot over 1 year ago

  • Fixed in Releases Katello 4.8.0 added
Actions #8

Updated by Partha Aji over 1 year ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF