I am trying to find out what packages are going to be updated if I run yum update -y on my content hosts that are attached to a foreman/katello server.
Right now there are no errata associated with the content host but there are installable updates. Is there any way to get the list of those packages (what versions are going to be applied and details of those packages, kind of what rpm -qi provides) from command line?
Right now I can see them in web interface but I have to keep proof for auditing purpose that āthe packages that are going to be updated have newer versionsā as seen from this output. Is there a way to achieve that? Maybe with any hammer sub command or pulp/katello command?
Almost every view in the UI for the Content menu is backed by an API call to the server, in this case the page that shows upgradeable packages can be viewed via:
Sorry I havenāt used the remote execution plugin before. Do you have an article/documentation/blog handy that I can use? The official remote execution documentation shows examples in the form of job templatesā¦
Unfortunately not in any stable release because this is a search parameter. For the 1.18/3.7 release stream of Foreman and Katello, work is being implemented that will document all known search parameter options and make that available via the API docs.
Sorry to come back to you piggybacking on the earlier question.
So, for SOX compliance, I have to show a screenshot or pdf file to the auditors. Something that canāt be tampered with. So, I am going to use the katello API from browser and instead of host_id I am going to use https://foreman_server/katello/api/v2/packages?host=my-hostname&packages_restrict_upgradable=true.
Now this will restrict the output to 20 per page. How do I pack all the packages in one single page that can be saved in a file?
Also, do you know how can I show which packages have been updated? Kind of same like packages_restrict_upgradable but post patching, not pre-patching.
I figured out that I can use https://foreman_server/katello/api/v2/packages?host=my-hostname&packages_restrict_upgradable=true&&per_page=<SOMELONGNUMBER> to see all packages in one go. Is that the only way?