Project

General

Profile

Actions
Copy link

Bug #14703

closed

hammer docker registry update lacks options for organization/location association

Added by Daniel Lobato Garcia about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Daniel Lobato Garcia
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
1327575
Pull request:
https://github.com/theforeman/foreman-docker/pull/160
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1327575
Description of problem:
hammer docker registry update lacks options for organization/location association. For other entities such as medium, domain, subnet, compute-resource these options exist.
For docker registries the only way is to use UI.

Version-Release number of selected component (if applicable):
@sat6.2.0-Beta-Snap8
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. # hammer docker registry update -h | grep -e location-ids -e locations -e organization-ids -e organizations

Actual results:
CLI: unable to associate docker registry with locations and organizations

Expected results:
CLI: docker registry update subcommand has similar options as other entities have for organization and location association

Actions
Copy link
 #1

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-docker/pull/160 added
Actions
Copy link
 #2

Updated by Daniel Lobato Garcia about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF