[major] Remove deprecated capabilities (#1233)

build/bin/copy-role-docs.sh

@@ -20,8 +20,6 @@ copyDoc aws_vpc
 copyDoc appconnect
 copyDoc cert_manager
 copyDoc cis
-copyDoc cluster_monitoring
-copyDoc convert_to_olm
 copyDoc common_services
 copyDoc configure_manage_eventstreams
 copyDoc cos
@@ -39,6 +37,7 @@ copyDoc gencfg_jdbc
 copyDoc gencfg_mongo
 copyDoc gencfg_watsonstudio
 copyDoc gencfg_workspace
+copyDoc grafana
 copyDoc ibm_catalogs
 copyDoc install_operator
 copyDoc kafka
@@ -48,6 +47,7 @@ copyDoc mirror_ocp
 copyDoc mirror_images
 copyDoc mongodb
 copyDoc nvidia_gpu
+copyDoc ocp_cluster_monitoring
 copyDoc ocp_config
 copyDoc ocp_contentsourcepolicy
 copyDoc ocp_deprovision
@@ -74,7 +74,6 @@ copyDoc suite_db2_setup_for_manage
 copyDoc suite_dns
 copyDoc suite_certs
 copyDoc suite_install
-copyDoc suite_install_digest_cm
 copyDoc suite_manage_bim_config
 copyDoc suite_manage_birt_report_config
 copyDoc suite_manage_customer_files_config
@@ -83,8 +82,6 @@ copyDoc suite_manage_import_certs_config
 copyDoc suite_manage_load_dbc_scripts
 copyDoc suite_manage_logging_config
 copyDoc suite_manage_pvc_config
-copyDoc suite_mustgather
-copyDoc suite_mustgather_download
 copyDoc suite_switch_to_olm
 copyDoc suite_upgrade
 copyDoc suite_rollback

docs/playbooks/oneclick-core.md

@@ -6,15 +6,14 @@ This playbook will install and configure IBM Maximo Application Suite Core along
 1. [Install IBM Operator Catalogs](../roles/ibm_catalogs.md) (1 minute)
 2. [Install IBM Common Services](../roles/common_services.md) (3 minutes)
 3. [Install Certificate Manager Operator](../roles/cert_manager.md) (3 minutes)
-4. [Configure Cluster Monitoring](../roles/cluster_monitoring.md) (1 minute)
-5. [Install Mongodb Operator and Create a Cluster](../roles/mongodb.md) (10 minutes)
-6. [Install and bootstrap IBM Suite License Service](../roles/sls.md) (10 minutes)
-7. [Install IBM User Data Services](../roles/uds.md) (30 minutes)
-8. [Generate a MAS Workspace Configuration](../roles/gencfg_workspace.md) (1 minute)
-9. [Configure Cloud Internet Services Integration for Maximo Application Suite](../roles/suite_dns.md) (Optional, 1 minute)
-10. [Install Maximo Application Suite Core Services](../roles/suite_install.md) (1 minute)
-11. [Configure Maximo Application Suite](../roles/suite_config.md) (1 minute)
-12. [Verify the Install and Configuration of Maximo Application Suite](../roles/suite_verify.md) (25 minutes)
+4. [Install Mongodb Operator and Create a Cluster](../roles/mongodb.md) (10 minutes)
+5. [Install and bootstrap IBM Suite License Service](../roles/sls.md) (10 minutes)
+6. [Install IBM User Data Services](../roles/uds.md) (30 minutes)
+7. [Generate a MAS Workspace Configuration](../roles/gencfg_workspace.md) (1 minute)
+8. [Configure Cloud Internet Services Integration for Maximo Application Suite](../roles/suite_dns.md) (Optional, 1 minute)
+9. [Install Maximo Application Suite Core Services](../roles/suite_install.md) (1 minute)
+10. [Configure Maximo Application Suite](../roles/suite_config.md) (1 minute)
+11. [Verify the Install and Configuration of Maximo Application Suite](../roles/suite_verify.md) (25 minutes)
 
 All timings are estimates, see the individual pages for each of these roles for more information and full details of all configuration options available in this playbook.
 
@@ -48,13 +47,9 @@ The other values can be left at their defaults.  Finally, click **Generate** and
 - `MAS_CONFIG_DIR` Directory where generated config files will be saved (you may also provide pre-generated config files here)
 - `SLS_LICENSE_ID` The license ID must match the license file available in `SLS_LICENSE_FILE`
 - `SLS_LICENSE_FILE` The path to the location of the license file.
-- `BAS_PROVIDER` Defines UDS or DRO operator to install. Default: DRO [Values: DRO, UDS]
-- `UDS_CONTACT_EMAIL` Defines the email for person to contact for UDS [Required if BAS_PROVIDER is UDS]
-- `UDS_CONTACT_FIRSTNAME` Defines the first name of the person to contact for UDS [Required if BAS_PROVIDER is UDS]
-- `UDS_CONTACT_LASTNAME` Defines the last name of the person to contact for UDS [Required if BAS_PROVIDER is UDS]
-- `DRO_CONTACT_EMAIL` Defines the email for person to contact for DRO [Required if BAS_PROVIDER is DRO]
-- `DRO_CONTACT_FIRSTNAME` Defines the first name of the person to contact for DRO [Required if BAS_PROVIDER is DRO]
-- `DRO_CONTACT_LASTNAME` Defines the last name of the person to contact for DRO [Required if BAS_PROVIDER is DRO]
+- `DRO_CONTACT_EMAIL` Primary contact e-mail address
+- `DRO_CONTACT_FIRSTNAME` Primary contact first name
+- `DRO_CONTACT_LASTNAME` Primary contact last name
 
 
 ### Storage Class Configuraton

docs/playbooks/uninstall-core.md

@@ -17,10 +17,10 @@ When using this playbook be sure that nothing else in your cluster is using any
 
 !!! warning
     This playbook will try to gracefully uninstall a target MAS instance by removing MAS related resources in the expected order.
-    Therefore, make sure your MAS operator is up and running in a healthy state, and no errors are reported in your `Suite` custom resource.  
-    
-    If there are any error reported in the logs of your MAS operator pod, or in your `Suite` custom resource, the uninstall process might get stuck and not complete successfully. In this case, you will need to debug and fix what is preventing your MAS operator to properly process the uninstall, or ultimately, forcibly uninstall MAS instance. 
-    
+    Therefore, make sure your MAS operator is up and running in a healthy state, and no errors are reported in your `Suite` custom resource.
+
+    If there are any error reported in the logs of your MAS operator pod, or in your `Suite` custom resource, the uninstall process might get stuck and not complete successfully. In this case, you will need to debug and fix what is preventing your MAS operator to properly process the uninstall, or ultimately, forcibly uninstall MAS instance.
+
     For more information regarding MAS uninstall process, refer to [Uninstalling Maximo Application Suite](https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=uninstalling) documentation.
 
 
@@ -30,10 +30,10 @@ Usage
 
 - `MAS_INSTANCE_ID` Declare the instance ID of MAS to remove
 
-### Required environment variables
+### Optional environment variables
 Any of these environment variables can be set to `none` to skip the uninstall of the associated dependency, this can be useful if you have multiple MAS instances installed on a single cluster for example.
 
-- `CLUSTER_MONITORING_ACTION`
+- `GRAFANA_ACTION`
 - `SLS_ACTION`
 - `MONGODB_ACTION`
 - `UDS_ACTION`
@@ -44,8 +44,6 @@ Any of these environment variables can be set to `none` to skip the uninstall of
 !!! warning
     Although you could set the actions to `install` and run the playbook it is strongly recommended not to as it runs through the dependencies in the reverse order that they need to be installed in; use the [oneclick-core](oneclick-core.md) playbook to repair a MAS Core installation.
 
-### Optional environment variables
-
 ### mas_wipe_mongo_data
 Defines whether Mongo databases should be deleted along with MAS uninstall