From e511c080270d0adf93443437b188f8c32b5b1ed1 Mon Sep 17 00:00:00 2001 From: Maximilian Kolb Date: Fri, 12 Sep 2025 09:00:41 +0200 Subject: [PATCH] Use Hammer CLI in favor of WebUI to change setting All steps but one relies on using CLI, so we should not force the user to complete this single step via WebUI. Tested on Foreman 3.14/Katello 4.16. --- ...guring-pull-based-transport-for-remote-execution.adoc | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/guides/common/modules/proc_configuring-pull-based-transport-for-remote-execution.adoc b/guides/common/modules/proc_configuring-pull-based-transport-for-remote-execution.adoc index adaddfb6ca9..1ca46985976 100644 --- a/guides/common/modules/proc_configuring-pull-based-transport-for-remote-execution.adoc +++ b/guides/common/modules/proc_configuring-pull-based-transport-for-remote-execution.adoc @@ -38,8 +38,13 @@ endif::[] include::snip_make-firewall-settings-persistent.adoc[] . In `pull-mqtt` mode, hosts subscribe for job notifications to either your {ProjectServer} or any {SmartProxyServer} through which they are registered. Ensure that {ProjectServer} sends remote execution jobs to that same {ProjectServer} or {SmartProxyServer}: -.. In the {ProjectWebUI}, navigate to *Administer* > *Settings*. -.. On the *Content* tab, set the value of *Prefer registered through {SmartProxy} for remote execution* to *Yes*. ++ +[options="nowrap", subs="+quotes,verbatim,attributes"] +---- +$ hammer settings set \ +--name remote_execution_prefer_registered_through_proxy \ +--value true +---- .Next steps * Configure your hosts for the pull-based transport.