Merge pull request #48136 from JStickler/OSSMDOC-607

JStickler · web-flow · commit 3243c4a6aca3 · 2022-07-29T09:56:14.000-04:00
OSSMDOC-607: Check Jaeger modules for content type attribute.
diff --git a/modules/jaeger-deploy-default.adoc b/modules/jaeger-deploy-default.adoc
@@ -1,8 +1,8 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-deploying.adoc
 ////
-
+:_content-type: PROCEDURE
 [id="jaeger-deploy-default_{context}"]
 = Deploying the default Jaeger strategy from the web console
 
diff --git a/modules/jaeger-deploy-production-es.adoc b/modules/jaeger-deploy-production-es.adoc
@@ -1,8 +1,8 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-deploying.adoc
 ////
-
+:_content-type: PROCEDURE
 [id="jaeger-deploy-production_{context}"]
 = Deploying the Jaeger production strategy from the web console
 
diff --git a/modules/jaeger-deploy-streaming.adoc b/modules/jaeger-deploy-streaming.adoc
@@ -1,8 +1,8 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-deploying.adoc
 ////
-
+:_content-type: PROCEDURE
 [id="jaeger-deploy-streaming_{context}"]
 = Deploying the Jaeger streaming strategy from the web console
 
diff --git a/modules/jaeger-deployment-best-practices.adoc b/modules/jaeger-deployment-best-practices.adoc
@@ -2,11 +2,9 @@
 This module included in the following assemblies:
 *  /jaeger/jaeger_install/rhbjaeger-deploying.adoc
 ////
-
+:pantheon-module-type: CONCEPT
 [id="jager-deployment-best-practices_{context}"]
 = Deployment best practices
-:pantheon-module-type: CONCEPT
-
 
 * Jaeger instance names must be unique. If you want to have multiple Jaeger instances and are using sidecar injected Jaeger agents, then the Jaeger instances should have unique names, and the injection annotation should explicitly specify the Jaeger instance name the tracing data should be reported to.
 
diff --git a/modules/jaeger-features.adoc b/modules/jaeger-features.adoc
@@ -1,10 +1,10 @@
 ////
-This CONCEPT module included in the following assemblies:
+This module included in the following assemblies:
 -service_mesh/v1x/ossm-architecture.adoc
 -service_mesh/v2x/ossm-architecture.adoc
 -rhbjaeger-architecture.adoc
 ////
-
+:pantheon-module-type: CONCEPT
 [id="jaeger-features_{context}"]
 = Jaeger features
 
diff --git a/modules/jaeger-install-elasticsearch.adoc b/modules/jaeger-install-elasticsearch.adoc
@@ -3,7 +3,6 @@
 // - service_mesh/v1x/installing-ossm.adoc
 // - rhbjaeger-installation.adoc
 
-
 :_content-type: PROCEDURE
 [id="jaeger-operator-install-elasticsearch_{context}"]
 = Installing the OpenShift Elasticsearch Operator
diff --git a/modules/jaeger-install-overview.adoc b/modules/jaeger-install-overview.adoc
@@ -1,7 +1,8 @@
 ////
-This CONCEPT module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-installation.adoc
 ////
+:pantheon-module-type: CONCEPT
 
 [id="jaeger-install-overview_{context}"]
 = Jaeger installation overview
diff --git a/modules/jaeger-install.adoc b/modules/jaeger-install.adoc
@@ -1,5 +1,5 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - service_mesh/v1x/installing-ossm.adoc
 - rhbjaeger-installation.adoc
 ////
diff --git a/modules/jaeger-removing-instance-cli.adoc b/modules/jaeger-removing-instance-cli.adoc
@@ -1,8 +1,8 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-installation.adoc
 ////
-
+:pantheon-module-type: PROCEDURE
 [id="jaeger-removing-cli_{context}"]
 = Removing a Jaeger instance from the CLI
 
diff --git a/modules/jaeger-removing-instance.adoc b/modules/jaeger-removing-instance.adoc
@@ -1,8 +1,8 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-removing.adoc
 ////
-
+:pantheon-module-type: PROCEDURE
 [id="jaeger-removing_{context}"]
 = Removing a Jaeger instance using the web console
 
diff --git a/modules/jaeger-sidecar-automatic.adoc b/modules/jaeger-sidecar-automatic.adoc
@@ -1,11 +1,10 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-deploying.adoc
 ////
-
+:pantheon-module-type: PROCEDURE
 [id="jaeger-sidecar-automatic_{context}"]
 = Automatically injecting sidecars
-:pantheon-module-type: PROCEDURE
 
 To enable this feature, you add the annotation `sidecar.jaegertracing.io/inject` set to either the string `true` or the Jaeger instance name as returned by `oc get jaegers`.
 When you specify `true`, there should be only a single Jaeger instance for the same namespace as the deployment, otherwise, the Operator cannot determine which Jaeger instance to use. A specific Jaeger instance name on a deployment has a higher precedence than `true` applied on its namespace.
diff --git a/modules/jaeger-sidecar-manual.adoc b/modules/jaeger-sidecar-manual.adoc
@@ -1,11 +1,10 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - rhbjaeger-deploying.adoc
 ////
-
+:pantheon-module-type: PROCEDURE
 [id="jaeger-sidecar-manual_{context}"]
 = Manually injecting sidecars
-:pantheon-module-type: PROCEDURE
 
 For controller types other than `Deployments` (for example, `StatefulSets`, `DaemonSets`, etc.), you can manually define the Jaeger Agent sidecar in your specification.
 
diff --git a/modules/jaeger-upgrading-es.adoc b/modules/jaeger-upgrading-es.adoc
@@ -1,8 +1,8 @@
 ////
-This PROCEDURE module included in the following assemblies:
+This module included in the following assemblies:
 - jaeger_install/rhbjaeger-updating
 ////
-
+:pantheon-module-type: PROCEDURE
 [id="upgrading_es5_es6_{context}"]
 = Upgrading from Elasticsearch 5 to Elasticsearch 6
 
