Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
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:


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.