Project

General

Profile

Feature #10181

hammer sync-plan-create and repository-set should use labels

Added by Bryan Kearney about 5 years ago. Updated 9 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Hammer
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1179356
I'm creating sync plans and repositories assignments among other things automatically via hammer tool.

e.g.:

$ hammer sync-plan create --interval=daily --name='Daily sync' --organization=$ORG

When I want to assign the sync plan to a product I need to list all sync plans, get an id and then assign the sync plan to product via the id because referencing of sync plan by name fails:

$ hammer product set-sync-plan --sync-plan='Daily sync' --organization=$ORG --name='Red Hat Enterprise Linux Server'
Could not assign synchronization plan.:
Error: option '--sync_plan_id' is required

The solution is to add --label option that will assign a tag to a sync plan or repository so that there is no ambiguity in sync plan/repo specification.

Needing to manually parse IDs is just a design flaw as there is no reason to even have --sync-plan, etc. options when they are ambiguous.

History

#1 Updated by Eric Helms almost 5 years ago

  • Legacy Backlogs Release (now unused) set to 70
  • Triaged changed from No to Yes

#2 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 70 to 86

#3 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 114

#4 Updated by John Mitsch 9 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF