Actions
Bug #31406
closed
As a user I 'd like to export library content
Difficulty:
Triaged:
Yes
Description
`hammer content-export library --organization-id=100`
- API
- Investigate whether the proposed hammer workflow could be achieved via API (and to what extent) * Make destination server optional/nullable (model change) * If incremental the export action should fetch the correct export history (either choose the latest for a given destination server or if history-id is provided use that ) * if you cant find an export history error out * history-id & destination server are optional.
- Hammer endpoint should
- Take in the organization id and optionally destination server
- Create a content view if necessary with a name like `Export-Library-<destination-server-name>-view` or `Export-Library-view` if destination server is not provided.
- Remove all the yum repositories this view
- Add all the yum repositories in library to this view
- Publish the content view
- Call Export on the generated content view version, with the same destination server as provided
Updated by The Foreman Bot about 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/9051 added
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/Katello/hammer-cli-katello/pull/763 added
Updated by Jonathon Turel about 4 years ago
- Category set to Content Views
- Target version set to Katello 3.18.0
- Triaged changed from No to Yes
Updated by The Foreman Bot about 4 years ago
- Fixed in Releases Katello 4.0.0 added
Updated by Partha Aji about 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|d81de1b96bd9450c3a8eb43166ff76becc8a56bb.
Actions