Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
The customer migrated the environment from puppet to Ansible, and they would like to remove all puppet classes using hammer or webconsole, but unfortunately hammer does not provide such functionality, but Satellite API can help here. Please check https://SATELLITE-FQDN/apidoc specifically DELETE /foreman_puppet/api/puppetclasses/:id  Delete a Puppet class and related methods that could help you to remove puppet related stuff.

Version-Release number of selected component (if applicable):
Satellite 6.13

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
There is no a method in hammer or Web Console to remove the puppet classes, the only way is using the Satellite API.

Expected results:
Remove the puppet classes using hammer command or through the Web console


Additional info:

On a side note, what do you mean by web console?

Hi,
AFAIK we don't have an endpoint for such an action for any other resources,
and we are not planning to add this kind of delete-all-resources endpoint.

Why doesn't the CU list all the puppet classes (their ids) and then simply
iterate over the list of ids, calling the API endpoint for deleting the resource?

(In reply to Adam Ruzicka from comment #1)
> On a side note, what do you mean by web console?

Satellite's Management Console

Thank you for submitting your feature proposal. After thorough consideration,
we have determined that the proposed feature is not aligned with the Satellite's scope and objectives.

We appreciate your contribution and encourage you to submit any other ideas or suggestions that may align more closely with our feature roadmap.