Merge pull request #329 from quixio/feature/sc-58235/external-source-destination-no-longer-in

tbedford · web-flow · commit 8c60bf16ec19 · 2024-05-10T16:08:50.000+01:00
External source is not available in code samples library
diff --git a/docs/develop/integrate-data/external-source.md b/docs/develop/integrate-data/external-source.md
@@ -2,34 +2,13 @@
 
 One simple way to write data into a Quix topic, is to use the prebuilt connector called `External source`. 
 
-To use the `External source` connector, step through the following procedure:
-
-1. In the UI click on `Code Samples` in the left-hand sidebar. 
-
-2. Search for `External source`. 
-
-3. Click `Add external source`.
-
-4. Select the output topic that you want to publish data to.
-
-5. Give your source a name.
+To add an external source:
 
+1. Go to the pipeline view.
+2. Click `+ New` in the top right corner of the view.
+3. Select `External source`.
+4. In `Output` select the topic you are going to publish to, or add a new topic with `+ Add new`. 
+5. In `Name` type any suitable name, such as "Laptop CPU Load".
 6. Click `Add external source`.
 
-7. In the Pipeline view click the newly created source and the following is displayed:
-
-    ![External source options](../../images/external-source-options.png){width=80%}
-
-8. For this example, select `HTTP API - JavaScript`. Code is generated for you that uses the Streaming Writer API (HTTP interface).
-
-9. Click the `Copy code` button to copy the code to your clipboard. 
-
-You can now paste the code into your JavaScript code, for example, your web browser client code. The code writes data into the Quix topic that you configured.
-
-As you can see there are other options such as generating Curl code that can be run in your shell to also write data into Quix. 
-
-The code samples generated are meant to provide you with a starting point from which you can build your own solutions. They provide a convenient way to see how the API works.
-
-## Next steps
-
-Further information can be found in the [Streaming Writer API](../../apis/streaming-writer-api/overview.md) documentation.
+The external source now appears in the pipeline view as a reminder (visual cue) as to the nature of the source generating the data for this topic.
diff --git a/docs/images/external-source-options.png b/docs/images/external-source-options.png
diff --git a/docs/quix-cloud/quixtour/external-source.md b/docs/quix-cloud/quixtour/external-source.md
@@ -4,43 +4,18 @@ At this point, you have completed the [Quickstart](../quickstart.md), and you ha
 
 However, you can't currently see this in the Pipeline view. To help you visualize what you've created, you add an external source component, to provide a visual entity in the pipeline view. 
 
-## Watch a video on adding an external source
-
-<div style="position: relative; padding-bottom: 62.24066390041494%; height: 0;"><iframe src="https://www.loom.com/embed/0c9be6ea1f9540618d8bf0c2dabc8533?sid=728b4cad-a224-4ffa-82fe-7f0bbe737779" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
-
-??? "Transcript"
-
-    0:01 Welcome back to another video. In this video I'll show you how to improve your pipeline view by creating an external source.
-
-    0:11 So let's go straight into it. The easiest way to do this, there's various ways that you can do this, but as you see there is a nice big box here, add external source, you can just click on that.
-    
-    0:28 The reason that I'm adding an external source is because my command line program that's capturing CPU load and publishing that into Quix is external to the Quix and environment.
-    
-    0:42 You'll see other examples where we use Quix's built-in code samples and connectors to build your pipeline, but they're internal to Quix, so you just use an ordinary source.
-    
-    0:57 So for our purposes here, we're going to create an example. External source. I'm going to call it server load, CPU load.
-    
-    1:10 You can call it anything you like really, as long as it makes sense to you. We also need to select the output topic.
-    
-    1:21 Well, we know the topic is CPU load because it's the only one we've got So let's go ahead and add that source now we can see The external source appears in the pipeline view And then later in the quick stall we're going to extend this pipeline So in the second part of the tour you'll add a transformation
-    
-    1:44 here and then when that's done on the other side of the transformation you'll create a destination to complete the pipeline.
-    
-    1:56 Okay that's it for this video thanks for watching and see you in the next video.
-
 ## How to add an external source
 
 To add an external source:
 
-1. Click on `Code Samples`.
-2. Select the `Source`, and `Basic templates` filters.
-3. On the `External Source` sample, click `Add external source`.
-4. Give the component a name, such as "Laptop CPU Load".
-5. For output topic select `cpu-load`.
+1. Go to the pipeline view.
+2. Click `+ New` in the top right corner of the view.
+3. Select `External source`.
+4. In `Output` select the topic you are going to publish to, or add a new topic with `+ Add new`. In this case select the `cpu-load` topic.
+5. In `Name` type any suitable name, such as "Laptop CPU Load".
 6. Click `Add external source`.
 
-This now appears in the pipeline view as a reminder (visual cue) as to the nature of the source generating the data for this topic.
-
+The external source now appears in the pipeline view as a reminder (visual cue) as to the nature of the source generating the data for this topic.
 
 ## 🏃‍♀️ Next step
 
diff --git a/docs/tutorials/event-detection/data-acquisition.md b/docs/tutorials/event-detection/data-acquisition.md
@@ -24,17 +24,12 @@ An external source is a representation of a data source that is external to Quix
 
 To add an external source:
 
-1. Navigate to the `Code Samples`.
-
-2. Under `Pipeline Stage` click `Source`.
-
-3. Locate the `External Source` sample and click `Add external source`.
-
-4. Enter `phone-data` in the `Output` field and click `Add new topic` in the dropdown.
-
-5. Enter `Quix companion web gateway` in the `Name` field.
-
-6. Click `Add external Source`.
+1. Go to the pipeline view.
+2. Click `+ New` in the top right corner of the view.
+3. Select `External source`.
+4. In `Output` select the topic you are going to publish to, or add a new topic with `+ Add new`. In this case select the `phone-data` topic.
+5. In `Name` type any suitable name, such as "Quix companion web gateway".
+6. Click `Add external source`.
 
 ### Install and configure the apps
 
diff --git a/docs/tutorials/influxdb-alerting/external-source.md b/docs/tutorials/influxdb-alerting/external-source.md
@@ -2,41 +2,15 @@
 
 At this point you have an external program sending data into Quix, and it is writing into a Quix topic. However, you can't see this external program in the Pipeline view. To help you visualize what you've created, you can add an external source component, to provide a visual entity in the pipeline view. To do this, log into Quix Cloud:
 
-1. Click on `Code Samples`.
-2. Select the `Python`, `Source`, and `Basic templates` filters.
-3. On the `External Source` sample, click `Add external source`.
-4. Give the component a name, such as "Laptop CPU Load".
-5. For output topic select `cpu-load`.
+1. Go to the pipeline view.
+2. Click `+ New` in the top right corner of the view.
+3. Select `External source`.
+4. In `Output` select the topic you are going to publish to, or add a new topic with `+ Add new`. In this case select the `cpu-load` topic.
+5. In `Name` type any suitable name, such as "Laptop CPU Load".
 6. Click `Add external source`.
 
 This now appears in the pipeline view as a reminder (visual cue) as to the nature of the source generating the data for this topic, and you can easily add further pipeline services on the output of this source.
 
-Watch a video on adding an external source:
-
-<div style="position: relative; padding-bottom: 62.24066390041494%; height: 0;"><iframe src="https://www.loom.com/embed/0c9be6ea1f9540618d8bf0c2dabc8533?sid=728b4cad-a224-4ffa-82fe-7f0bbe737779" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
-
-??? "Transcript"
-
-    0:01 Welcome back to another video. In this video I'll show you how to improve your pipeline view by creating an external source.
-
-    0:11 So let's go straight into it. The easiest way to do this, there's various ways that you can do this, but as you see there is a nice big box here, add external source, you can just click on that.
-
-    0:28 The reason that I'm adding an external source is because my command line program that's capturing CPU load and publishing that into Quix is external to the Quix and environment.
-
-    0:42 You'll see other examples where we use Quix's built-in code samples and connectors to build your pipeline, but they're internal to Quix, so you just use an ordinary source.
-
-    0:57 So for our purposes here, we're going to create an example. External source. I'm going to call it server load, CPU load.
-
-    1:10 You can call it anything you like really, as long as it makes sense to you. We also need to select the output topic.
-
-    1:21 Well, we know the topic is CPU load because it's the only one we've got So let's go ahead and add that source now we can see The external source appears in the pipeline view And then later in the quick stall we're going to extend this pipeline So in the second part of the tour you'll add a transformation
-
-    1:44 here and then when that's done on the other side of the transformation you'll create a destination to complete the pipeline.
-
-    1:56 Okay that's it for this video thanks for watching and see you in the next video.
-
-Note, this video is for a different project, but the principle is the same.
-
 ## 🏃‍♀️ Next step
 
 [Part 3 - Add InfluxDB destination :material-arrow-right-circle:{ align=right }](./influxdb-destination.md)
