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:
This RFE also implies that multiple export jobs should be able to run simultaneously.
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.