Merge pull request #101659 from otikhomi/OSDOCS-16122-adding-missing-content-types-rosa

jneczypor · web-flow · commit 3b2818317e74 · 2025-11-05T11:04:15.000-08:00
OSDOCS-16122 - Adding missing content types to ROSA
diff --git a/_attributes/attributes-openshift-dedicated.adoc b/_attributes/attributes-openshift-dedicated.adoc
@@ -1,3 +1,4 @@
+:_mod-docs-content-type: SNIPPET
 // General Service Delivery Attributes attributes
 :toc:
 :toc-title:
diff --git a/modules/dedicated-aws-dc-methods.adoc b/modules/dedicated-aws-dc-methods.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-dc.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="dedicated-aws-dc-methods"]
 = AWS Direct Connect methods
 
diff --git a/modules/dedicated-aws-vpc-peering-terms.adoc b/modules/dedicated-aws-vpc-peering-terms.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-peering.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="dedicated-aws-vpc-peering-terms"]
 = VPC peering terms
 
diff --git a/modules/dedicated-aws-vpn-troubleshooting.adoc b/modules/dedicated-aws-vpn-troubleshooting.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-vpn.adoc
 
+:_mod-docs-content-type: PROCEDURE
 [id="dedicated-aws-vpn-troubleshooting"]
 = Troubleshooting the VPN connection
 
diff --git a/modules/mos-network-prereqs-min-bandwidth.adoc b/modules/mos-network-prereqs-min-bandwidth.adoc
@@ -4,6 +4,7 @@
 // * rosa_planning/rosa-cloud-expert-prereq-checklist.adoc
 // * rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="mos-network-prereqs-min-bandwidth_{context}"]
 = Minimum bandwidth
 
diff --git a/modules/rosa-architecture.adoc b/modules/rosa-architecture.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_architecture/rosa_architecture_sub/rosa-architecture-models.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-classic-architecture_{context}"]
 = {product-title}
 
diff --git a/modules/rosa-aws-customer-managed-policies.adoc b/modules/rosa-aws-customer-managed-policies.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_architecture/rosa-sts-about-iam-resources.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-aws-customer-managed-policies_{context}"]
 = Customer-managed policies
 {product-title} (ROSA) users are able to attach customer-managed policies to the IAM roles required to run and maintain ROSA clusters. This capability is not uncommon with AWS IAM roles.
diff --git a/modules/rosa-aws-iam.adoc b/modules/rosa-aws-iam.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-iam_{context}"]
 = Red{nbsp}Hat managed IAM references for AWS
 
diff --git a/modules/rosa-aws-provisioned.adoc b/modules/rosa-aws-provisioned.adoc
@@ -3,6 +3,7 @@
 // * rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc
 // * rosa_planning/rosa-sts-aws-prereqs.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-aws-policy-provisioned_{context}"]
 = Provisioned AWS Infrastructure
 
diff --git a/modules/rosa-aws-requirements.adoc b/modules/rosa-aws-requirements.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-customer-requirements_{context}"]
 = Customer Requirements
 
diff --git a/modules/rosa-aws-scp.adoc b/modules/rosa-aws-scp.adoc
@@ -3,6 +3,7 @@
 // * rosa_architecture/rosa-sts-about-iam-resources.adoc
 // * rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-minimum-scp_{context}"]
 = Minimum set of effective permissions for service control policies (SCP)
 
diff --git a/modules/rosa-checking-account-version-cli-version.adoc b/modules/rosa-checking-account-version-cli-version.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cli/rosa-checking-acct-version-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-version_{context}"]
 = version
 
diff --git a/modules/rosa-checking-account-version-cli-whoami.adoc b/modules/rosa-checking-account-version-cli-whoami.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cli/rosa-checking-acct-version-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-whoami_{context}"]
 = whoami
 
diff --git a/modules/rosa-configure.adoc b/modules/rosa-configure.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_cli/rosa-get-started-cli.adoc
 
+:_mod-docs-content-type: PROCEDURE
 [id="rosa-configure_{context}"]
 = Configuring the ROSA CLI
 
diff --git a/modules/rosa-configuring-autorepair.adoc b/modules/rosa-configuring-autorepair.adoc
@@ -4,7 +4,7 @@
 // * nodes/rosa-managing-worker-nodes.adoc
 //
 
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: CONCEPT
 [id="rosa-configuring-autorepair_{context}"]
 = Configuring machine pool AutoRepair
 
diff --git a/modules/rosa-delete-objects.adoc b/modules/rosa-delete-objects.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cli/rosa-manage-objects-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-delete-objects_{context}"]
 = Delete objects
 
@@ -87,7 +88,7 @@ ifdef::openshift-rosa[]
 [id="rosa-delete-autoscaler_{context}"]
 == delete autoscaler
 
-Deletes autoscaler configuration for a given cluster. 
+Deletes autoscaler configuration for a given cluster.
 
 [NOTE]
 ====
@@ -534,7 +535,7 @@ $ rosa delete upgrade
 .Arguments
 [cols="30,70"]
 |===
-|Option 
+|Option
 |Definition
 
 |-c, --cluster string
diff --git a/modules/rosa-edit-objects.adoc b/modules/rosa-edit-objects.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_cli/rosa-manage-objects-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-edit-objects_{context}"]
 = Edit objects
 
diff --git a/modules/rosa-getting-started-configure-an-idp-and-grant-access.adoc b/modules/rosa-getting-started-configure-an-idp-and-grant-access.adoc
@@ -3,6 +3,7 @@
 // * rosa_getting_started/rosa-getting-started.adoc
 // * rosa_getting_started/rosa-quickstart-guide-ui.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-getting-started-configure-an-idp-and-grant-access_{context}"]
 = Configuring an identity provider and granting cluster access
 
diff --git a/modules/rosa-getting-started-environment-setup.adoc b/modules/rosa-getting-started-environment-setup.adoc
@@ -4,6 +4,7 @@
 // * rosa_getting_started/rosa-quickstart-guide-ui.adoc
 // * rosa_hcp/rosa-hcp-quickstart-guide.adoc
 
+:_mod-docs-content-type: PROCEDURE
 [id="rosa-getting-started-environment-setup_{context}"]
 = Setting up the environment
 
diff --git a/modules/rosa-getting-started-revoking-admin-privileges-and-user-access.adoc b/modules/rosa-getting-started-revoking-admin-privileges-and-user-access.adoc
@@ -3,6 +3,7 @@
 // * rosa_getting_started/rosa-getting-started.adoc
 // * rosa_getting_started/rosa-quickstart-guide-ui.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-getting-started-revoking-admin-privileges-and-user-access_{context}"]
 = Revoking administrator privileges and user access
 
diff --git a/modules/rosa-hcp-architecture.adoc b/modules/rosa-hcp-architecture.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_architecture/rosa_architecture_sub/rosa-architecture-models.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-hcp-architecture_{context}"]
 = {product-title} with HCP architecture
 
diff --git a/modules/rosa-hcp-aws-private-security-groups.adoc b/modules/rosa-hcp-aws-private-security-groups.adoc
@@ -2,15 +2,15 @@
 //
 // * rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc
 
-[id="rosa-hcp-aws-private-security-groups_{context}"]
 :_mod-docs-content-type: PROCEDURE
+[id="rosa-hcp-aws-private-security-groups_{context}"]
 = Adding additional AWS security groups to the AWS PrivateLink endpoint
 
 With {product-title} clusters, the AWS PrivateLink endpoint exposed in the host's Virtual Private Cloud (VPC) has a security group that limits access to requests that originate from within the cluster's Machine CIDR range. You must create and attach another security group to the PrivateLink endpoint to grant API access to entities outside of the VPC through VPC peering, transit gateways, or other network connectivity.
 
 [IMPORTANT]
 ====
-Adding additional AWS security groups to the AWS PrivateLink endpoint is only supported on {product-title} version 4.17.2 and later. 
+Adding additional AWS security groups to the AWS PrivateLink endpoint is only supported on {product-title} version 4.17.2 and later.
 ====
 
 .Prerequisites
diff --git a/modules/rosa-hcp-firewall-prerequisites.adoc b/modules/rosa-hcp-firewall-prerequisites.adoc
@@ -3,6 +3,7 @@
 // * rosa_planning/rosa-sts-aws-prereqs.adoc
 // * rosa_planning/rosa-hcp-prereqs.adoc <-- this is a symlink
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-hcp-firewall-prerequisites_{context}"]
 = Firewall prerequisites for {product-title}
 
@@ -57,7 +58,7 @@
 
 |`access.redhat.com`
 |443
-|Required. Hosts a signature store that a container client requires for verifying images when pulling them from `registry.access.redhat.com`. 
+|Required. Hosts a signature store that a container client requires for verifying images when pulling them from `registry.access.redhat.com`.
 
 |`api.openshift.com`
 |443
@@ -102,7 +103,7 @@ For more information about how remote health monitoring data is used by Red{nbsp
 --
 1. This can also be accomplished by configuring a private interface endpoint in your AWS Virtual Private Cloud (VPC) to the regional AWS STS endpoint.
 --
- 
+
 == Domains for your workload
 
 Your workload may require access to other sites that provide resources for programming languages or frameworks.
diff --git a/modules/rosa-hcp-vpc-manual.adoc b/modules/rosa-hcp-vpc-manual.adoc
@@ -9,7 +9,7 @@ ifeval::["{context}" == "rosa-hcp-egress-zero-install"]
 :rosa-egress-lockdown:
 endif::[]
 
-:_mod-docs-content-type: PREFERENCE
+:_mod-docs-content-type: REFERENCE
 [id="rosa-hcp-vpc-manual_{context}"]
 = Creating an AWS Virtual Private Cloud manually
 
diff --git a/modules/rosa-initialize.adoc b/modules/rosa-initialize.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_cli/rosa-get-started-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-initialize_{context}"]
 = Initializing {product-title}
 
diff --git a/modules/rosa-install-uninstall-addon.adoc b/modules/rosa-install-uninstall-addon.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_cli/rosa-manage-objects-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-install-uninstall-addon_{context}"]
 = Install and uninstall add-ons
 
diff --git a/modules/rosa-logs-install.adoc b/modules/rosa-logs-install.adoc
@@ -2,6 +2,7 @@
 //
 // * * rosa_cli/rosa-checking-logs-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-logs-install_{context}"]
 = logs install
 
diff --git a/modules/rosa-logs-uninstall.adoc b/modules/rosa-logs-uninstall.adoc
@@ -2,6 +2,7 @@
 //
 // * * rosa_cli/rosa-checking-logs-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-logs-uninstall_{context}"]
 = logs uninstall
 
diff --git a/modules/rosa-oidc-config-overview.adoc b/modules/rosa-oidc-config-overview.adoc
@@ -3,6 +3,7 @@
 // * rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc
 // * rosa_architecture/rosa-sts-about-iam-resources.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-byo-odic-overview_{context}"]
 = Creating an OpenID Connect Configuration
 
diff --git a/modules/rosa-parent-commands.adoc b/modules/rosa-parent-commands.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_cli/rosa-manage-objects-cli.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="rosa-parent-commands_{context}"]
 = Parent commands
 
diff --git a/modules/rosa-planning-environment-application-reqs.adoc b/modules/rosa-planning-environment-application-reqs.adoc
@@ -1,6 +1,8 @@
 // Module included in the following assemblies:
 //
 // * rosa_planning/rosa-planning-environment.adoc
+
+:_mod-docs-content-type: REFERENCE
 [id="planning-environment-application-requirements_{context}"]
 = Planning your environment based on application requirements
 
diff --git a/modules/rosa-planning-environment-cluster-max.adoc b/modules/rosa-planning-environment-cluster-max.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_planning/rosa-planning-environment.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="planning-environment-cluster-maximums_{context}"]
 = Planning your environment based on tested cluster maximums
 
diff --git a/modules/rosa-policy-change-management.adoc b/modules/rosa-policy-change-management.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-shared-responsibility.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-change-management_{context}"]
 = Change management
 
diff --git a/modules/rosa-policy-customer-responsibility.adoc b/modules/rosa-policy-customer-responsibility.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-customer-responsibility_{context}"]
 = Additional customer responsibilities for data and applications
 
diff --git a/modules/rosa-policy-disaster-recovery.adoc b/modules/rosa-policy-disaster-recovery.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-shared-responsibility.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-disaster-recovery_{context}"]
 = Disaster recovery
 Disaster recovery includes data and configuration backup, replicating data and configuration to the disaster recovery environment, and failover on disaster events.
diff --git a/modules/rosa-policy-failure-points.adoc b/modules/rosa-policy-failure-points.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-understand-availability.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-failure-points_{context}"]
 = Potential points of failure
 
diff --git a/modules/rosa-policy-incident.adoc b/modules/rosa-policy-incident.adoc
@@ -2,6 +2,8 @@
 // Module included in the following assemblies:
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-shared-responsibility.adoc
+
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-incident_{context}"]
 = Incident and operations management
 
diff --git a/modules/rosa-policy-security-and-compliance.adoc b/modules/rosa-policy-security-and-compliance.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-shared-responsibility.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-security-compliance_{context}"]
 = Security and regulation compliance
 The following table outlines the  the responsibilities in regards to security and regulation compliance:
diff --git a/modules/rosa-policy-security-regulation-compliance.adoc b/modules/rosa-policy-security-regulation-compliance.adoc
@@ -3,6 +3,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-security-regulation-compliance_{context}"]
 = Security and regulation compliance
 
diff --git a/modules/rosa-policy-shared-responsibility.adoc b/modules/rosa-policy-shared-responsibility.adoc
@@ -2,6 +2,7 @@
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="rosa-policy-shared-responsibility_{context}"]
 = Tasks for shared responsibilities by area
 
diff --git a/modules/rosa-prereq-roles-overview.adoc b/modules/rosa-prereq-roles-overview.adoc
@@ -2,7 +2,7 @@
 // * rosa_planning/rosa-sts-ocm-role.adoc
 // * rosa_planning/rosa-hcp-prepare-iam-roles-resources.adoc
 
-:_mod-docs-content-type: MODULE
+:_mod-docs-content-type: REFERENCE
 [id="rosa-prereq-roles-overview_{context}"]
 = Overview of required roles
 
diff --git a/modules/rosa-quickstart-instructions.adoc b/modules/rosa-quickstart-instructions.adoc
@@ -2,7 +2,7 @@
 //
 // * rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-quickstart.adoc
 
-
+:_mod-docs-content-type: REFERENCE
 [id="rosa-quickstart-instructions"]
 = Command quick reference list
 
diff --git a/modules/rosa-required-aws-service-quotas.adoc b/modules/rosa-required-aws-service-quotas.adoc
diff --git a/modules/rosa-requirements-deploying-in-opt-in-regions.adoc b/modules/rosa-requirements-deploying-in-opt-in-regions.adoc
diff --git a/modules/rosa-sdpolicy-logging.adoc b/modules/rosa-sdpolicy-logging.adoc
diff --git a/modules/rosa-sdpolicy-monitoring.adoc b/modules/rosa-sdpolicy-monitoring.adoc
diff --git a/modules/rosa-sdpolicy-networking.adoc b/modules/rosa-sdpolicy-networking.adoc
diff --git a/modules/rosa-sdpolicy-platform.adoc b/modules/rosa-sdpolicy-platform.adoc
diff --git a/modules/rosa-sdpolicy-security.adoc b/modules/rosa-sdpolicy-security.adoc
diff --git a/modules/rosa-sdpolicy-storage.adoc b/modules/rosa-sdpolicy-storage.adoc
diff --git a/modules/rosa-sts-account-wide-role-and-policy-commands.adoc b/modules/rosa-sts-account-wide-role-and-policy-commands.adoc
diff --git a/modules/rosa-sts-account-wide-roles-and-policies.adoc b/modules/rosa-sts-account-wide-roles-and-policies.adoc
diff --git a/modules/rosa-sts-operator-role-commands.adoc b/modules/rosa-sts-operator-role-commands.adoc
diff --git a/modules/rosa-troubleshooting-installing.adoc b/modules/rosa-troubleshooting-installing.adoc
diff --git a/modules/sd-ingress-responsibilities.adoc b/modules/sd-ingress-responsibilities.adoc
diff --git a/modules/sd-planning-cluster-maximums-environment.adoc b/modules/sd-planning-cluster-maximums-environment.adoc
diff --git a/modules/sd-planning-cluster-maximums.adoc b/modules/sd-planning-cluster-maximums.adoc
diff --git a/modules/sd-planning-considerations.adoc b/modules/sd-planning-considerations.adoc
diff --git a/snippets/mobb-support-statement.adoc b/snippets/mobb-support-statement.adoc
diff --git a/snippets/rosa-sts.adoc b/snippets/rosa-sts.adoc
