Merge pull request #79801 from EricPonvelle/OSDOCS-11394_External-ID-Flag

OSDOCS#11394: Added documentation for the External ID flag

Author: EricPonvelle

modules/rosa-create-objects.adoc

@@ -235,6 +235,9 @@ If the argument is not supplied, an autogenerated value is created that depends
 |--etcd-encryption-kms-arn
 |Enables encryption of ETCD storage using the customer-managed key managed in AWS Key Management Service.
 
+|--external-id <arn_string>
+|An optional unique identifier that might be required when you assume a role in another account.
+
 |--host-prefix <subnet>
 |The subnet prefix length to assign to each individual node, as an integer. For example, if host prefix is set to `23`, then each node is assigned a `/23` subnet out of the given CIDR.
 

modules/rosa-hcp-sts-creating-a-cluster-cli.adoc

@@ -37,11 +37,13 @@ When creating a {hcp-title} cluster, the default machine Classless Inter-Domain
 +
 * If you did not set environmental variables, run the following command:
 +
+--
 [source,terminal]
 ----
-$ rosa create cluster --cluster-name=<cluster_name> \ <.>
-    --mode=auto --hosted-cp [--private] \ <.> 
-    --operator-roles-prefix <operator-role-prefix> \ <.>
+$ rosa create cluster --cluster-name=<cluster_name> \ <1>
+    --mode=auto --hosted-cp [--private] \ <2> 
+    --operator-roles-prefix <operator-role-prefix> \ <3>
+    --external-id <external-id> \ <4>
     --oidc-config-id <id-of-oidc-configuration> \ 
     --subnet-ids=<public-subnet-id>,<private-subnet-id>
 ----
@@ -53,7 +55,9 @@ $ rosa create cluster --cluster-name=<cluster_name> \ <.>
 ====
 If you specified custom ARN paths when you created the associated account-wide roles, the custom path is automatically detected. The custom path is applied to the cluster-specific Operator roles when you create them in a later step.
 ====
-+
+<.> Optional: A unique identifier that might be required when you assume a role in another account.
+--
+
 * If you set the environmental variables, create a cluster with a single, initial machine pool, using either a publicly or privately available API, and a publicly or privately available Ingress by running the following command:
 +
 [source,terminal]

modules/rosa-list-objects.adoc

@@ -681,6 +681,9 @@ $ rosa describe cluster --cluster=<cluster_name> | <cluster_id> [arguments]
 |--debug
 |Enables debug mode.
 
+|--external-id <arn_string>
+|An optional unique identifier that might be required when you assume a role in another account.
+
 |--profile
 |Specifies an AWS profile (string) from your credentials file.