Skip to content

Commit 7b49e82

Browse files
authored
JC-587-2 remove refs to addon (#490)
* JC-587-2 remove refs to addon * JC-587-2 update link in yaml * JC-587-2 update link in yaml 2
1 parent 0d1c747 commit 7b49e82

File tree

3 files changed

+18
-13
lines changed

3 files changed

+18
-13
lines changed

docs/connectors/getting-started-connectors/README.adoc

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ ifdef::context[:parent-context: {context}]
6161

6262
// Purpose statement for the assembly
6363
[role="_abstract"]
64-
As a developer of applications and services, you can use {product-long-connectors} to create and configure connections between OpenShift Streams for Apache Kafka and third-party systems.
64+
As a developer of applications and services, you can use {product-long-connectors} to create and configure connections between {product-long-kafka} and third-party systems.
6565

6666
In this example, you connect a data source (a data generator) that creates Kafka messages and a data sink (an HTTP endpoint) that consumes the Kafka messages.
6767

@@ -181,12 +181,14 @@ Click the card to select the connector, and then click *Next*.
181181
+
182182
NOTE: If you have not already configured a {product-kafka} instance for Connectors, you can create a new Kafka instance by clicking *Create Kafka instance*. You would also need to set up and define access for a service account as described in _Configuring the {product-kafka} instance for use with {product-long-connectors}_.
183183

184-
. On the *Namespace* page, the namespace that you select depends on your OpenShift Dedicated environment.
185-
+
186-
If you are using a trial cluster in your own OpenShift Dedicated environment, select the card for the namespace that was created when you added the Connectors service to your trial cluster, as described in _https://access.redhat.com/documentation/en-us/red_hat_openshift_connectors/TBD[Adding the OpenShift Connectors service to an OpenShift Dedicated trial cluster^]_.
184+
. On the *Namespace* page, click *Register eval namespace* to provision a namespace for hosting the Connectors instances that you create.
185+
186+
//. On the *Namespace* page, the namespace that you select depends on your OpenShift Dedicated environment.
187+
//+
188+
//If you are using a trial cluster in your own OpenShift Dedicated environment, select the card for the namespace that was created when you added the Connectors service to your trial cluster, as described in _https://access.redhat.com/documentation/en-us/red_hat_openshift_connectors/TBD[Adding the OpenShift Connectors service to an OpenShift Dedicated trial cluster^]_.
187189
//need to update this link with correct URL
188-
+
189-
If you are using the evaluation OpenShift Dedicated environment, click *Register eval namespace* to provision a namespace for hosting the Connectors instances that you create.
190+
//+
191+
//If you are using the evaluation OpenShift Dedicated environment, click *Register eval namespace* to provision a namespace for hosting the Connectors instances that you create.
190192

191193
. Click *Next*.
192194

@@ -253,11 +255,13 @@ endif::[]
253255
+
254256
For example, select *test* and then click *Next*.
255257

256-
. On the *Namespace* page, the namespace that you select depends on your OpenShift Dedicated environment.
257-
+
258-
If you are using a trial cluster on your own OpenShift Dedicated environment, select the card for the namespace that was created when you added the Connectors service to your trial cluster.
259-
+
260-
If you are using the evaluation OpenShift Dedicated environment, click the *eval namespace* that you created when you created the source connector.
258+
. On the *Namespace* page, click the *eval namespace* that you created when you created the source connector.
259+
260+
//. On the *Namespace* page, the namespace that you select depends on your OpenShift Dedicated environment.
261+
//+
262+
//If you are using a trial cluster on your own OpenShift Dedicated environment, select the card for the namespace that was created when you added the Connectors service to your trial cluster.
263+
//+
264+
//If you are using the evaluation OpenShift Dedicated environment, click the *eval namespace* that you created when you created the source connector.
261265

262266
. Click *Next*.
263267

docs/connectors/getting-started-connectors/quickstart.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ kind: QuickStarts
33
metadata:
44
name: connectors-getting-started
55
annotations:
6-
draft: true
6+
draft: false
77
order: 6
88
spec:
99
version: 0.1
@@ -18,7 +18,7 @@ spec:
1818
prerequisites:
1919
- A Red Hat identity
2020
- You've created a Kafka instance and the instance is in `Ready` state. See the _Getting started with OpenShift Streams for Apache Kafka_ quick start.
21-
- For the data sink example, open the free Webhook.site (https://webhook.site) in a browser window. The Webhook.site page provides a unique URL that you copy. You use this URL as an HTTP data sink.
21+
- For the data sink example, open the free <a href="https://webhook.site">Webhook.site</a> in a browser window. The Webhook.site page provides a unique URL that you copy. You use this URL as an HTTP data sink.
2222
introduction: !snippet README.adoc#introduction
2323
tasks:
2424
- !snippet/proc README.adoc#proc-configuring-kafka-for-connectors

docs/registry/getting-started-registry/quickstart.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ kind: QuickStarts
33
metadata:
44
name: getting-started-service-registry
55
annotations:
6+
draft: true
67
order: 1
78
spec:
89
version: 0.1

0 commit comments

Comments
 (0)