Merge pull request #102834 from bergerhoffer/pr-102735-cp417

[enterprise-4.17] OSDOCS#17381: Adding blank lines after includes

Author: bergerhoffer

applications/application-health.adoc

@@ -24,6 +24,7 @@ include::modules/odc-monitoring-application-health-using-developer-perspective.a
 // cannot add health checks in web console
 ifdef::openshift-rosa,openshift-dedicated[]
 include::modules/odc-adding-health-checks.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-dedicated[]
 
 include::modules/odc-editing-health-checks.adoc[leveloffset=+1]

applications/connecting_applications_to_services/binding-workloads-using-sbo.adoc

@@ -37,8 +37,11 @@ spec:
 As shown in the previous example, you can also directly use a `ConfigMap` or a `Secret` itself as a service resource to be used as a source of binding data.
 
 include::modules/sbo-naming-strategies.adoc[leveloffset=+1]
+
 include::modules/sbo-advanced-binding-options.adoc[leveloffset=+1]
+
 include::modules/sbo-binding-workloads-that-are-not-compliant-with-PodSpec.adoc[leveloffset=+1]
+
 include::modules/sbo-unbinding-workloads-from-a-backing-service.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

applications/connecting_applications_to_services/exposing-binding-data-from-a-service.adoc

@@ -13,9 +13,13 @@ Application developers need access to backing services to build and connect work
 The {servicebinding-title} enables application developers to easily bind workloads together with operator-managed backing services, without any manual procedures to configure the binding connection. For the {servicebinding-title} to provide the binding data, as an Operator provider or user who creates backing services, you must expose the binding data to be automatically detected by the {servicebinding-title}. Then, the {servicebinding-title} automatically collects the binding data from the backing service and shares it with a workload to provide a consistent and predictable experience.
 
 include::modules/sbo-methods-of-exposing-binding-data.adoc[leveloffset=+1]
+
 include::modules/sbo-data-model.adoc[leveloffset=+1]
+
 include::modules/sbo-setting-annotations-mapping-optional.adoc[leveloffset=+1]
+
 include::modules/sbo-rbac-requirements.adoc[leveloffset=+1]
+
 include::modules/sbo-categories-of-exposable-binding-data.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

applications/connecting_applications_to_services/projecting-binding-data.adoc

@@ -17,6 +17,7 @@ After the backing service exposes the binding data, for a workload to access and
 . As environment variables, after you configure the `.spec.bindAsFiles` parameter from the `ServiceBinding` resource.
 
 include::modules/sbo-configuration-of-directory-path-to-project-binding-data.adoc[leveloffset=+1]
+
 include::modules/sbo-projecting-the-binding-data.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

applications/connecting_applications_to_services/understanding-service-binding-operator.adoc

@@ -13,8 +13,11 @@ Application developers need access to backing services to build and connect work
 The {servicebinding-title} enables application developers to easily bind workloads together with Operator-managed backing services, without any manual procedures to configure the binding connection.
 
 include::modules/sbo-service-binding-terminology.adoc[leveloffset=+1]
+
 include::modules/sbo-about-service-binding-operator.adoc[leveloffset=+1]
+
 include::modules/sbo-key-features.adoc[leveloffset=+1]
+
 include::modules/sbo-api-differences.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

applications/deployments/deployment-strategies.adoc

@@ -27,12 +27,16 @@ A deployment strategy uses readiness checks to determine if a new pod is ready f
 
 // Rolling strategies
 include::modules/deployments-rolling-strategy.adoc[leveloffset=+1]
+
 include::modules/deployments-canary-deployments.adoc[leveloffset=+2]
+
 // Creating rolling deployments
 include::modules/creating-rolling-deployments-CLI.adoc[leveloffset=+2]
+
 // Editing a deployment
 :context: rolling-strategy
 include::modules/odc-editing-deployments.adoc[leveloffset=+2]
+
 // Starting a deployment
 include::modules/odc-starting-rolling-deployment.adoc[leveloffset=+2]
 
@@ -43,9 +47,11 @@ include::modules/odc-starting-rolling-deployment.adoc[leveloffset=+2]
 
 // Recreate strategies
 include::modules/deployments-recreate-strategy.adoc[leveloffset=+1]
+
 // Editing a deployment
 :context: recreate-strategy
 include::modules/odc-editing-deployments.adoc[leveloffset=+2]
+
 // Starting a deployment
 include::modules/odc-starting-recreate-deployment.adoc[leveloffset=+2]
 
@@ -56,6 +62,7 @@ include::modules/odc-starting-recreate-deployment.adoc[leveloffset=+2]
 
 // Custom strategies
 include::modules/deployments-custom-strategy.adoc[leveloffset=+1]
+
 // Editing a deployment
 :context: custom-strategy
 include::modules/odc-editing-deployments.adoc[leveloffset=+2]

applications/deployments/managing-deployment-processes.adoc

@@ -14,13 +14,21 @@ include::snippets/deployment-config-deprecated.adoc[]
 `DeploymentConfig` objects can be managed from the {product-title} web console's *Workloads* page or using the `oc` CLI. The following procedures show CLI usage unless otherwise stated.
 
 include::modules/deployments-starting-deployment.adoc[leveloffset=+2]
+
 include::modules/deployments-viewing-deployment.adoc[leveloffset=+2]
+
 include::modules/deployments-retrying-deployment.adoc[leveloffset=+2]
+
 include::modules/deployments-rolling-back.adoc[leveloffset=+2]
+
 include::modules/deployments-exec-cmd-in-container.adoc[leveloffset=+2]
+
 include::modules/deployments-viewing-logs.adoc[leveloffset=+2]
+
 include::modules/deployments-triggers.adoc[leveloffset=+2]
+
 include::modules/deployments-setting-triggers.adoc[leveloffset=+3]
+
 include::modules/deployments-setting-resources.adoc[leveloffset=+2]
 
 // When the Nodes book is added to ROSA/OSD, check if this link is valid.
@@ -32,14 +40,17 @@ ifndef::openshift-rosa,openshift-dedicated[]
 endif::openshift-rosa,openshift-dedicated[]
 
 include::modules/deployments-scaling-manually.adoc[leveloffset=+2]
+
 include::modules/deployments-accessing-private-repos.adoc[leveloffset=+2]
 
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 include::modules/deployments-assigning-pods-to-nodes.adoc[leveloffset=+2]
+
 endif::[]
 
 ifndef::openshift-online[]
 include::modules/deployments-running-pod-svc-acct.adoc[leveloffset=+2]
+
 endif::[]
 
 ////

applications/deployments/rosa-config-custom-domains-applications.adoc

@@ -14,4 +14,5 @@ Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To
 You can configure a custom domain for your applications. Custom domains are specific wildcard domains that can be used with {product-title} applications. 
 
 include::modules/rosa-applications-config-custom-domains.adoc[leveloffset=+1]
+
 include::modules/rosa-applications-renew-custom-domains.adoc[leveloffset=+1]

applications/deployments/route-based-deployment-strategies.adoc

@@ -28,10 +28,15 @@ A canary deployment tests the new version but when a problem is detected it quic
 The route-based deployment strategies do not scale the number of pods in the services. To maintain desired performance characteristics the deployment configurations might have to be scaled.
 
 include::modules/deployments-proxy-shards.adoc[leveloffset=+1]
+
 include::modules/deployments-n1-compatibility.adoc[leveloffset=+1]
+
 include::modules/deployments-graceful-termination.adoc[leveloffset=+1]
+
 include::modules/deployments-blue-green.adoc[leveloffset=+1]
+
 include::modules/deployments-ab-testing.adoc[leveloffset=+1]
+
 include::modules/deployments-ab-testing-lb.adoc[leveloffset=+2]
 
 [role="_additional-resources"]

applications/deployments/what-deployments-are.adoc

@@ -45,13 +45,17 @@ If the existing deployment strategies are not suited for your use case and you m
 The following sections provide further details on these objects.
 
 include::modules/deployments-replicasets.adoc[leveloffset=+2]
+
 include::modules/deployments-replicationcontrollers.adoc[leveloffset=+2]
 
 include::modules/deployments-kube-deployments.adoc[leveloffset=+1]
+
 include::modules/deployments-deploymentconfigs.adoc[leveloffset=+1]
 
 include::modules/deployments-comparing-deploymentconfigs.adoc[leveloffset=+1]
+
 include::modules/deployment-specific-features.adoc[leveloffset=+2]
+
 include::modules/deploymentconfig-object-specific-features.adoc[leveloffset=+2]
 
 ////