Allow webhooks in containerized deployments

Author: adamruzicka

guides/common/assembly_using-foreman-webhooks.adoc

@@ -14,6 +14,7 @@ include::modules/proc_creating-a-webhook.adoc[leveloffset=+1]
 
 include::modules/ref_webhooks-available-events.adoc[leveloffset=+1]
 
+ifndef::containerized[]
 include::modules/con_shellhooks-plugin-for-smartproxy.adoc[leveloffset=+1]
 
 include::modules/proc_installing-shellhooks-plugin.adoc[leveloffset=+1]
@@ -23,6 +24,7 @@ include::modules/proc_passing-arguments-to-shellhook-script-using-webhooks.adoc[
 include::modules/proc_passing-arguments-to-shellhook-script-using-curl.adoc[leveloffset=+1]
 
 include::modules/proc_creating-a-shellhook-to-print-arguments.adoc[leveloffset=+1]
+endif::[]
 
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]

guides/common/modules/con_webhooks-behavior-and-integration.adoc

@@ -15,10 +15,12 @@ The application sending the request does not wait for the response, or ignores i
 Because webhooks use HTTP, no new infrastructure needs be added to existing web services.
 Webhooks are useful where the action you want to perform in the external system can be achieved through its API.
 
+ifndef::containerized[]
 Where it is necessary to run additional commands or edit files, the shellhooks plugin for {SmartProxies} is available.
 The shellhooks plugin enables you to define a shell script on the {SmartProxy} that can be executed through the API.
 
 You can use webhooks successfully without installing the shellhooks plugin.
+endif::[]
 
 Payload of a webhook is created from webhook templates.
 Webhook templates use the same ERB syntax as Provisioning templates.

guides/common/modules/proc_creating-a-webhook.adoc

@@ -6,12 +6,15 @@
 [role="_abstract"]
 When creating a webhook in the {ProjectWebUI}, you can customize events, payloads, HTTP authentication, content type, and headers.
 
+TODO: Fact check - is this relevant in containers?
 ifndef::foreman-deb,orcharhino[]
+ifndef::containerized[]
 [NOTE]
 ====
 When configuring webhooks with endpoints with non-standard HTTP or HTTPS ports, an SELinux port must be assigned, see {InstallingServerDocURL}configuring-selinux-to-ensure-access-on-custom-ports_{project-context}[Configuring SELinux to ensure access to {Project} on custom ports] in _{InstallingServerDocTitle}_.
 ====
 endif::[]
+endif::[]
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Administer* > *Webhook* > *Webhooks*.

guides/common/modules/proc_installing-webhooks-plugin.adoc

@@ -10,6 +10,13 @@ Then, you can configure {ProjectServer} to send webhook requests.
 .Procedure
 . On your {ProjectServer}, install the webhooks plugin:
 +
+ifdef::containerized[]
+[options="nowrap" subs="+quotes,attributes"]
+----
+# {foremanctl} --add-feature webhooks
+----
+endif::[]
+ifndef::containerized[]
 [options="nowrap" subs="+quotes,attributes"]
 ----
 # {foreman-installer} --enable-foreman-plugin-webhooks
@@ -20,3 +27,4 @@ Then, you can configure {ProjectServer} to send webhook requests.
 ----
 # {foreman-installer} --enable-foreman-cli-webhooks
 ----
+endif::[]

guides/common/modules/ref_webhooks-available-events.adoc

@@ -12,6 +12,7 @@ For more information about payload, go to *Administer* > *About* > *Support* > *
 A list of available types is provided in the following table.
 Some events are marked as *custom*, in that case, the payload is an object object but a Ruby hash (key-value data structure) so syntax is different.
 
+TODO: What to do with this, considering some plugins providing events are not containerized yet? Be diligent or just wait it out?
 [cols="40%,30%,30%",options="header"]
 |====
 |Event name |Description|Payload

guides/doc-Administering_Project/master.adoc

@@ -94,9 +94,11 @@ include::common/assembly_monitoring-project-resources.adoc[leveloffset=+1]
 ifndef::satellite[]
 include::common/assembly_limiting-host-resources.adoc[leveloffset=+1]
 endif::[]
+endif::[]
 
 include::common/assembly_using-foreman-webhooks.adoc[leveloffset=+1]
 
+ifndef::satellite[]
 include::common/assembly_working-efficiently-with-web-ui.adoc[leveloffset=+1]
 
 [appendix]