Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

With the release of 6.5, we are deprecating hammer-csv. It will be removed in 6.6.

All Hammer-csv sub-commands have been updated with deprecation warning except following:

activationkeys
content-hosts
export
import
settings
subscriptions

It makes sense to add the one liner deprecation warning to above sub-commands when we already covered rest of all. There are chances where customer can directly jump on utility without looking at docs. 

Atleast hammer-csv --help - should show the deprecation warning.

@BK: please see comment5. Can we fix it please ?

Verified ON_QA

Update: BZ #1706906 is created to flag the Hammer CSV as deprecated in the Satellite 6.5 Release Notes.

Update: BZ #1706909 is created to add a deprecation note to the Hammer CLI Guide (section 10.14 Hammer CSV)

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:1222