Description of problem:
The API has support to list autosign entries (GET /api/v2/smart_proxies/:id/autosign), but lacks support to create and update existing entries.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Be able to use the API to create and update autosign entries.
Also the support to create and update autosign entries using the hammer CLI is missing.
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Connecting redmine issue http://projects.theforeman.org/issues/4986 from this bug
Moving 6.2 bugs out to sat-backlog.
having the ability to create autosign entries via the API would greatly simplify the process of running bootstrap.py on existing hosts. Today we make the user either
- setup autosigning in autosign.conf
- approve the client manually in the UI.
I would prefer to not have to do either.
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/7495 has been resolved.
As per the API doc shows, these are the endpoints available for this action now:
"List all autosign entries": "/api/smart_proxies/smart_proxy_id/autosign",
"Create autosign entry": "/api/smart_proxies/:smart_proxy_id/autosign",
"Delete autosign entry": "/api/smart_proxies/:smart_proxy_id/autosign/:id"
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.