Add snippet content type (theforeman#4626)

* Add snippet content type

* Add separate repo snippet for each build

* Move procedure heading from snippet to module

* Move verification from snippet to module

* Update module type

* Add + signs

* Drop a snippet that is only used once

* Drop dlist headings that did not work with the snippet attr

* Add + to prevent an attr from showing

* Drop symlink in favor of a regular include

---------

Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>

Author: aneta-petrova

guides/common/assembly_installing-capsule-server.adoc

@@ -22,7 +22,7 @@ ifdef::satellite[]
 include::modules/proc_configuring-repositories-proxy.adoc[leveloffset=+1]
 endif::[]
 ifndef::satellite[]
-include::modules/con_configuring-repositories.adoc[leveloffset=+1]
+include::modules/proc_configuring-repositories.adoc[leveloffset=+1]
 endif::[]
 
 // Installing {SmartProxyServer} Packages

guides/common/assembly_installing-server-connected.adoc

@@ -10,7 +10,7 @@ ifdef::satellite[]
 include::modules/proc_registering-to-red-hat-subscription-management.adoc[leveloffset=+1]
 endif::[]
 
-include::modules/con_configuring-repositories.adoc[leveloffset=+1]
+include::modules/proc_configuring-repositories.adoc[leveloffset=+1]
 
 include::modules/con_considerations-for-using-the-foreman-installer-utility.adoc[leveloffset=+1]
 

guides/common/assembly_preparing-smartproxyservers-for-load-balancing.adoc

@@ -20,7 +20,7 @@ ifdef::satellite[]
 include::modules/proc_configuring-repositories-proxy.adoc[leveloffset=+1]
 endif::[]
 ifndef::satellite[]
-include::modules/con_configuring-repositories.adoc[leveloffset=+1]
+include::modules/proc_configuring-repositories.adoc[leveloffset=+1]
 endif::[]
 
 // Installing {SmartProxyServer} Packages

guides/common/modules/con_configuring-repositories.adoc

@@ -21,6 +21,7 @@ The provisioned machine must appear on the same network as your provisioning inf
 +
 You can integrate a compute resource with {Project} and let the compute resource create virtual machines through this integration.
 You can also provision virtual machines from unintegrated infrastructure as you would bare-metal machines.
++
 include::snip_prerequisites-common-compute-resource.adoc[]
 
 [role="_additional-resources"]

guides/common/modules/con_prerequisites-for-network-boot-provisioning.adoc

@@ -18,4 +18,5 @@ ifndef::orcharhino[]
 For more information, see xref:preparing-networking[].
 endif::[]
 * An existing VMware template if you want to use image-based provisioning.
++
 include::snip_prerequisites-common-compute-resource.adoc[]

guides/common/modules/con_prerequisites-for-vmware-provisioning.adoc

@@ -13,6 +13,7 @@ endif::[]
 Before you can provision cloud instances on Google Compute Engine, ensure that your environment meets the following requirements:
 
 include::snip_prerequisite-networking-for-provisioning.adoc[]
++
 include::snip_prerequisites-common-compute-resource.adoc[]
 * In your GCE project, configure a service account with the necessary IAM Compute role.
 For more information, see https://cloud.google.com/compute/docs/access/iam[Compute Engine IAM roles] in the GCE documentation.

guides/common/modules/con_provisioning-cloud-instances-on-google-compute-engine.adoc

@@ -41,6 +41,7 @@ EOS
 . In the {ProjectWebUI}, navigate to *Hosts* > *Operating systems* and select the operating system that you want for your host.
 . Click the *Templates* tab, and from the *Finish Template* list, select your finish template.
 . In the {ProjectWebUI}, navigate to *Hosts* > *Create Host*.
++
 include::snip_steps-create-a-host-tab-host.adoc[]
 . Click the *Parameters* tab and navigate to *Host parameters*.
 ifdef::katello,satellite,orcharhino[]

guides/common/modules/proc_configuring-a-finish-template-for-amazon-ec2.adoc

@@ -11,6 +11,7 @@ This does not use SSH and hosts do not require opening up any incoming firewall
 * You have registered the host to {Project}.
 * The {SmartProxy} through which the host is registered is configured to use `pull-mqtt` mode.
 For more information, see {InstallingSmartProxyDocURL}configuring-pull-based-transport-for-remote-execution_{smart-proxy-context}[Configuring pull-based transport for remote execution] in _{InstallingSmartProxyDocTitle}_.
++
 include::snip_prerequisite-project-client-repository-enabled.adoc[]
 ifdef::satellite[]
 * The AppStream repository for the operating system version of the host is synchronized on {ProjectServer}, available in the content view and the lifecycle environment of the host, and enabled for the host.

guides/common/modules/proc_configuring-a-host-to-use-the-pull-client.adoc

@@ -57,4 +57,17 @@ ifndef::foreman-deb[]
 # restorecon -RvF /var/lib/tftpboot/
 ----
 endif::[]
-include::snip_step-set-bootstrap-http-url.adoc[]
+. Set the HTTP URL.
+* If you want to use {ProjectServer} for booting, reconfigure your {ProjectServer}:
++
+[options="nowrap" subs="+quotes,attributes"]
+----
+# {foreman-installer} \
+--foreman-proxy-dhcp-ipxefilename "http://_{foreman-example-com}_/unattended/iPXE?bootstrap=1"
+----
+* If you want to use {SmartProxyServer} for booting, reconfigure your {SmartProxyServer}:
++
+[options="nowrap" subs="+quotes,attributes"]
+----
+# {foreman-installer} --foreman-proxy-dhcp-ipxe-bootstrap true
+----