Project

Profile

Help

Story #186

closed

RFE: --all option for "rpm repo sync schedules delete"

Added by rbowlby83@gmail.com about 9 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

++ This bug was initially created as a clone of Bugzilla Bug #959033 ++

Description of problem:

Description of problem:

Two requests regarding rpm schedule management.

1. --all option for delete

Deleting scheduled syncs for several repositories is unnecessarily involved. An example:

repos=$(pulp-admin rpm repo list | grep ^Id | grep mobi | awk '{print $2 }')

for r in $repos; do sched_id=$(pulp-admin rpm repo sync schedules list --repo-id $r | grep ^Id | awk '{print $2}'); pulp-admin rpm repo sync schedules delete --schedule-id $sched_id --repo-id $r; done

That's quite a bit of work when with an --all option it would be just this:

pulp-admin rpm repo list | grep ^Id | grep mobi | awk '{print $2 }' | xargs pulp-admin rpm repo sync schedules delete --all --repo-id

2. Make --repo-id optional when you specify a --schedule-id, assuming the schedule-id is globally unique then there's no reason to additionally require the repo-id. It's quite a bit more work when managing the schedule of multiple repos (the common pattern).

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

2.1.1-0.5.beta.el6.noarch

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

--- Additional comment from at 05/08/2013 20:23:26 ---

Ryan, Even though 2 RFEs or bugs are in the same area, we advise opening up separate bugs for each request. I have created https://bugzilla.redhat.com/show_bug.cgi?id=961114 and cc'd you on that one. Feel free to add more details over there.

--- Additional comment from at 05/08/2013 20:25:05 ---

This is an RFE to handle --all flag as per request 1 in the description of the bug. Request 2 is tracked separately in https://bugzilla.redhat.com/show_bug.cgi?id=961114.

Also available in: Atom PDF