Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1336096 - [RFE] add export-dir as option for repository and content-view export hammer command
Summary: [RFE] add export-dir as option for repository and content-view export hammer ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-14 06:46 UTC by Fred van Zwieten
Modified: 2016-05-14 08:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-14 08:49:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fred van Zwieten 2016-05-14 06:46:37 UTC 
Description of problem:
Currently, export is guided towards the pulp_export_dir which is global. I would like to specify the export directory per hammer export command. ie:

hammer content-view version export --id 3 --environment PROD --export-dir=<spec>

when not specified the global setting applies.

There are usecases outside of ISS which could use this option. Suppose you would like to update remote and offline systems from a laptop. You can export the repo's in a content-view to the laptop and have those systems updated from that laptop. In this case the laptop's filesystem is mounted to the satellite server on a mount-point and export-dir would refer to ths mount-point. Now image multiple users would like to do this concurrently. That would mean the need to use per user mountpoints and per command export-dirs.

Version-Release number of selected component (if applicable):
6.2 BETA

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
alternatively, an envionment variable could be used, but that would be less ideal

Additional info:
Comment 1 Fred van Zwieten 2016-05-14 07:59:36 UTC 
This RFE also implies that multiple export jobs should be able to run simultaneously.
Comment 2 Fred van Zwieten 2016-05-14 08:49:29 UTC 
Actually, i'm going to close this as a (better) alternative is to just run the export to a fixed location and rsync that to wherever and whenever you want.
Note You need to log in before you can comment on or make changes to this bug.