docs: Update credential info in guides (#549)

* docs: replace real creds

* docs: update two more occurrences of real creds

Author: jbyrne-redhat

docs/kafka/rhoas-cli-getting-started-kafka/README.adoc

@@ -191,11 +191,11 @@ view the `credentials.json` file that you created.
 +
 --
 .Example `credentials.json` file
-[source,json,subs="+attributes"]
+[source,json,subs="+attributes,+quotes"]
 ----
 {
-	"clientID":"srvc-acct-8c95ca5e1225-94a-41f1-ab97-aacf3df1",
-	"clientSecret":"facf3df1-ab97-2253-aa87-ab97",
+	"clientID":"_<client-id>_",
+	"clientSecret":"_<client-secret>_",
     "oauthTokenUrl": "{sso-token-url}"
 }
 ----
@@ -205,13 +205,13 @@ You use these credentials and the bootstrap server URL to connect your applicati
 . Set the permissions for your service account to access the Kafka instance resources.
 +
 --
-This example allows applications to produce and consume messages from topics starting with a specified prefix that belong to any consumer group. The service account information you input here is the 'clientID' from the previous step.
+This example allows applications to produce and consume messages from topics starting with a specified prefix that belong to any consumer group. The service account information you input here is the `clientID` value from the previous step.
 
 .Assigning access permissions to a service account
-[source,shell]
+[source,shell,subs="+quotes"]
 ----
 $ rhoas kafka acl grant-access --consumer --producer \
-    --service-account srvc-acct-8c95ca5e1225-94a-41f1-ab97-aacf3df1 --topic-prefix myapp  --group all
+    --service-account _<client-id>_ --topic-prefix myapp  --group all
 ----
 
 The permissions you assign depend on whether your application produces or consumes messages.

docs/registry/rhoas-cli-getting-started-registry/README.adoc

@@ -195,11 +195,11 @@ view the `credentials.json` file that you created.
 +
 --
 .Example `credentials.json` file
-[source,json,subs="+attributes"]
+[source,json,subs="+attributes,+quotes"]
 ----
 {
-	"clientID":"srvc-acct-8c95ca5e1225-94a-41f1-ab97-aacf3df1",
-	"clientSecret":"facf3df1-ab97-2253-aa87-ab97",
+	"clientID":"_<client-id>_",
+	"clientSecret":"_<client-secret>_",
     "oauthTokenUrl": "{sso-token-url}"
 }
 ----
@@ -217,9 +217,9 @@ By connecting your applications to your {registry} instance, you can retrieve ar
 This example creates a role called `manager` for the service account.
 
 .Creating a role for the service account
-[source,shell]
+[source,shell,subs="+quotes"]
 ----
-$ rhoas service-registry role add --role=manager --service-account=srvc-acct-8c95ca5e1225-94a-41f1-ab97-aacf3df1
+$ rhoas service-registry role add --role=manager --service-account=_<client-id>_
 ----
 --
 

docs/rhoas/rhoas-service-contexts/README.adoc

@@ -292,19 +292,19 @@ $ cp ./producer/.env ./consumer/.env
 For a service context with single Kafka and {registry} instances, the `.env` file looks like the following example:
 +
 .Example environment variables file for connection configuration information
-[source,shell,subs="+attributes"]
+[source,shell,subs="+attributes,+quotes"]
 ----
-## Generated by rhoas cli
+\\## Generated by rhoas cli
 ## Kafka Configuration
 KAFKA_HOST=kafka-inst-cafkr-jma--lhulbl-ca.bf2.kafka.rhcloud.com:443
-## Service Registry Configuration
+\\## Service Registry Configuration
 SERVICE_REGISTRY_URL=https://bu98.serviceregistry.rhcloud.com/t/0aa1dd8b-63d5-466c-9de8-7c03320a81c2
 SERVICE_REGISTRY_CORE_PATH=/apis/registry/v2
 SERVICE_REGISTRY_COMPAT_PATH=/apis/ccompat/v6
 
 ## Authentication Configuration
-RHOAS_CLIENT_ID=srvc-acct-14295e3c-f72d-4bae-876c-3172a96eb7eb
-RHOAS_CLIENT_SECRET=5c3a20e0-d946-4edf-94d2-35db41f3b2ad
+RHOAS_CLIENT_ID=_<client-id>_
+RHOAS_CLIENT_SECRET=_<client-secret>_
 RHOAS_OAUTH_TOKEN_URL={sso-token-url}
 ----
 +
@@ -313,19 +313,19 @@ As shown in the example, the file that you generate contains the endpoints for y
 . Set Access Control List (ACL) permissions to enable the new service account to access resources in the Kafka instance.
 +
 .Example command for granting access to Kafka instance
-[source,shell]
+[source,shell,subs="+quotes"]
 ----
-$ rhoas kafka acl grant-access --producer --consumer --service-account srvc-acct-14295e3c-f72d-4bae-876c-3172a96eb7eb --topic quotes --group all
+$ rhoas kafka acl grant-access --producer --consumer --service-account _<client-id>_ --topic quotes --group all
 ----
 +
 The command you entered allows applications to use the service account to produce and consume messages in the `quotes` topic. Applications can use any consumer group and producer.
 
 . Use Role-Based Access Control (RBAC) to enable the new service account to access the {registry} instance and the artifacts (such as schemas) that it contains.
 +
 .Example command for granting access to {registry} instance
-[source,shell]
+[source,shell,subs="+quotes"]
 ----
-$ rhoas service-registry role add --role manager --service-account srvc-acct-14295e3c-f72d-4bae-876c-3172a96eb7eb
+$ rhoas service-registry role add --role manager --service-account _<client-id>_
 ----
 
 . In the guides and samples repository, navigate to the directory for the producer component. Use Apache Maven to run the producer component in developer mode.