Bug 1263997 - [RFE] foreman-rake export_tasks shall support exporting a single task
[RFE] foreman-rake export_tasks shall support exporting a single task
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Tasks Plugin (Show other bugs)
6.1.2
Unspecified Unspecified
medium Severity medium (vote)
: Unspecified
: --
Assigned To: Ivan Necas
: FutureFeature
Depends On:
Blocks: 1122832 260381
  Show dependency treegraph
 
Reported: 2015-09-17 05:38 EDT by Peter Vreman
Modified: 2017-04-05 11:21 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-04-05 11:21:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Vreman 2015-09-17 05:38:50 EDT
Description of problem:
Currently foreman-rake export_tasks supports only ALL tasks or all non-successful tasks.
This can be very slow when many tasks are in the system. It also means that mean non-relevant (and disattracting) tasks are included for Bug reporting.

Please add a possibility to filter on a list of specified tasks:

foreman-rake export_tasks tasks=8533bdf0-51be-4d7b-a2bb-c9eec7066a44,e335026f-2f00-4045-9971-e63cd0320f51


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


How reproducible:


Steps to Reproduce:
1. Export a single task
2.
3.

Actual results:
All tasks are exports, you need to look in the final .tar.gz to strip out unneeded information

Expected results:
.tar.gz contains only the data of the selected tasks


Additional info:
Comment 1 Ivan Necas 2017-04-05 11:21:08 EDT
This is possible in 6.2.x releases, using TASK_SEARCH field, example:

  foreman-rake foreman_tasks:export_tasks TASK_SEARCH='id = 667250a0-6d98-4fb4-800b-4a2c97da79de'

See foreman-rake -D foreman_tasks:export_tasks for more details

Note You need to log in before you can comment on or make changes to this bug.