Merge pull request #73962 from mletalie/OSDOCS-10073

[OSDOCS-10073]Update documentation: Expose cluster delete protection feature (ROSA CLI)

Author: EricPonvelle

modules/rosa-edit-objects.adoc

@@ -31,6 +31,13 @@ $ rosa edit cluster --cluster=<cluster_name> | <cluster_id> [arguments]
 |--private
 |Restricts a primary API endpoint to direct, private connectivity.
 
+|--enable-delete-protection=true
+|Enables the delete protection feature.
+
+|--enable-delete-protection=false
+|Disables the delete protection feature.
+
+
 |===
 
 .Optional arguments inherited from parent commands
@@ -85,19 +92,19 @@ $ rosa edit ingress --cluster=<cluster_name> | <cluster_id> [arguments]
 |--cluster
 |Required: The name or ID (string) of the cluster to which the ingress will be added.
 
-|--cluster-routes-hostname  
+|--cluster-routes-hostname
 |Components route hostname for OAuth, console, and download.
 
-|--cluster-routes-tls-secret-ref 
+|--cluster-routes-tls-secret-ref
 |Components route TLS secret reference for OAuth, console, and download.
 
-|--excluded-namespaces 
+|--excluded-namespaces
 |Excluded namespaces for ingress. Format is a comma-separated list `value1, value2...`. If no values are specified, all namespaces will be exposed.
 
 |--label-match
 |The label match (string) for ingress. The format must be a comma-delimited list of key=value pairs. If no label is specified, all routes are exposed on both routers.
 
-|--lb-type  
+|--lb-type
 |Type of Load Balancer. Options are `classic`, `nlb`.
 
 |--namespace-ownership-policy
@@ -109,7 +116,7 @@ $ rosa edit ingress --cluster=<cluster_name> | <cluster_id> [arguments]
 |--route-selector
 |Route Selector for ingress. Format is a comma-separated list of key=value. If no label is specified, all routes will be exposed on both routers. For legacy ingress support these are inclusion labels, otherwise they are treated as exclusion label.
 
-|--wildcard-policy 
+|--wildcard-policy
 |Wildcard Policy for ingress. Options are `WildcardsDisallowed` and `WildcardsAllowed`. Default is `WildcardsDisallowed`.
 |===
 

rosa_install_access_delete_clusters/rosa-sts-deleting-cluster.adoc

@@ -40,5 +40,6 @@ include::modules/rosa-unlinking-and-deleting-ocm-and-user-iam-roles.adoc[levelof
 [id="additional-resources_rosa-sts-deleting-cluster"]
 == Additional resources
 
+* For information about the cluster delete protection feature, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-edit-objects_rosa-managing-objects-cli[Edit objects].
 * For information about the AWS IAM resources for ROSA clusters that use STS, see xref:../rosa_architecture/rosa-sts-about-iam-resources.adoc#rosa-sts-about-iam-resources[About IAM resources for ROSA clusters that use STS].
 * For information on cluster errors that are due to missing IAM roles, see xref:../support/troubleshooting/rosa-troubleshooting-deployments.adoc#rosa-troubleshooting-cluster-deletion_rosa-troubleshooting-cluster-deployments[Repairing a cluster that cannot be deleted].