Description of problem: Spacewalk supports SSL certificates and keys on a per-repo basis; although their selection is available via the Spacewalk web client, such functionality is not exposed by spacecmd. Adding this will likely implicate the modification of repo_create and repo_details. It may also require the creation of commands that correspond to repo_rename and repo_updateurl.
Taking...
spacewalk.git: e1c5895 1287246 - spacecmd: repo_details show 'None' if repository doesn't have SSL Certtificate e45dc7a 1287246 - Added fixes to API methods a4b2a21 1287246 - spacecmd: Added functions to add/edit SSL certificates for repositories fa8cb26 1287246 - Added new API methods to add new repository with SSL certificates or update existing one Changes to fix: 0) Added/Changed API Methods to add/set SSL Certificates for repositories: 1) 'repo_change' command was changed, so now it's possible to specify SSL Certificates (but it's not necessary), e.g.: repo_create: Create a user repository usage: repo_create <options> options: -n, --name name of repository -u, --url url of repository --ca SSL CA certificate (not required) --cert SSL Client certificate (not required) --key SSL Client key (not required) 2) added new command 'repo_updatessl', e.g.: repo_updatessl: Change the SSL certificates of a user repository usage: repo_updatessl <options> options: --ca SSL CA certificate (not required) --cert SSL Client certificate (not required) --key SSL Client key (not required) 3) added changes to command 'repo_details', so it can show details about SSL certificates
Spacewalk 2.5 was released.
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.