Description of problem:

I've been looking at ways to create a 'clone' (note: not backup) of a
Sat6 server.  There is a Sat6 in one environment but I would
like the same configuration (with a different Org + Locations) in a
separate environment which has no direct network connectivity with the
other apart from Sat6-A -> Local Desktop -> USB drive ->  Laptop on
network B -> Sat6-B.

Hammer --csv is great for exporting details of all the required metadata
but I've noticed that the naming convention for Repositories and
Repository Sets are different.

A worked example:

On Sat6-A
# hammer product list --organization-id=3 --enabled yes

My "Red Hat Enterprise Linux Server" has the product-id of 105.

# hammer --csv repository list --product-id 105 --organization-id=3 >
repoList.csv
Shows:
Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server
Red Hat Enterprise Linux 7 Server - Extras RPMs x86_64
Red Hat Enterprise Linux 7 Server Kickstart x86_64 7Server
Red Hat Enterprise Linux 7 Server - Optional RPMs x86_64 7Server
etc,etc

I then copy repoList.csv over the Sat6-B

If I then try to enable one of the repos on Sat6-B using:
hammer repository-set enable  --organization "${ORG}" \
  --product "Red Hat Enterprise Linux Server" \
  --name "Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server" \
  --releasever "7Server" --basearch "x86_64"

It fails because the correct name of the repo is "Red Hat Enterprise
Linux 7 Server (RPMs)".  There doesn't seem to be a neat way of getting
the 'right' repo names from the ones outputed.

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

How reproducible:


Steps to Reproduce:
1. See Above
2.
3.

Actual results:
See Above

Expected results:
See Above

Additional info:
Is it possible for hammer --csv repository list to output the same name as required for hammer repository-set enable ?