Project

General

Profile

Bug #11213

for katello the sync-plan create --sync-date doesnt actually default

Added by Greg Swift almost 5 years ago. Updated 9 months ago.

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

Description

> sync-plan create --help
..snip..
 --sync-date SYNC_DATE                   start date and time of the synchronization *defaults to now*
                                         Date and time in YYYY-MM-DD HH:MM:SS or ISO 8601 format
..snip..
> sync-plan create --name Weekly --enabled yes --interval weekly --organization-id 1
Could not create the sync plan:
  Missing arguments for 'sync_date'
> sync-plan create --name Weekly --enabled yes --interval weekly --organization-id 1 --sync-date "2015-07-25 00:00:00" 
Sync plan created

History

#1 Updated by Dominic Cleal almost 5 years ago

  • Project changed from Hammer CLI to Katello
  • Category set to Hammer
  • Legacy Backlogs Release (now unused) deleted (35)
  • Triaged set to No

#2 Updated by Eric Helms almost 5 years ago

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

#3 Updated by Stephen Benjamin almost 5 years ago

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

Mass move to 2.4.0

#4 Updated by Justin Sherrill over 4 years ago

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

#5 Updated by Eric Helms about 4 years ago

  • Assignee set to Zach Huntington-Meath

#6 Updated by Eric Helms about 4 years ago

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

#7 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