This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k-examples.git


The following commit(s) were added to refs/heads/master by this push:
     new 77cba13  Added Azure Storage Queue quickstart
     new f362784  Merge pull request #26 from luigidemasi/ENTESB-14040
77cba13 is described below

commit 77cba138a8957a2a47b2417661906b062582b809
Author: Luigi De Masi <ldem...@redhat.com>
AuthorDate: Wed Jul 29 19:21:36 2020 +0200

    Added Azure Storage Queue quickstart
---
 .../azure-storage-queue-channel.yaml               |   7 +
 .../azure-storage-queue-consumer.groovy            |   9 +
 .../azure-storage-queue-producer.groovy            |  11 ++
 .../azure-storage-queue-source.yaml                |  31 ++++
 .../azure-storage-queue.properties                 |   3 +
 09-azure-storage-queue-basic/readme.didact.md      | 181 +++++++++++++++++++++
 09-azure-storage-queue-basic/readme.md             | 181 +++++++++++++++++++++
 7 files changed, 423 insertions(+)

diff --git a/09-azure-storage-queue-basic/azure-storage-queue-channel.yaml 
b/09-azure-storage-queue-basic/azure-storage-queue-channel.yaml
new file mode 100644
index 0000000..8cda507
--- /dev/null
+++ b/09-azure-storage-queue-basic/azure-storage-queue-channel.yaml
@@ -0,0 +1,7 @@
+#
+# Knative Channel
+#
+apiVersion: messaging.knative.dev/v1alpha1
+kind: InMemoryChannel
+metadata:
+  name: azure-queue
diff --git a/09-azure-storage-queue-basic/azure-storage-queue-consumer.groovy 
b/09-azure-storage-queue-basic/azure-storage-queue-consumer.groovy
new file mode 100644
index 0000000..19af50c
--- /dev/null
+++ b/09-azure-storage-queue-basic/azure-storage-queue-consumer.groovy
@@ -0,0 +1,9 @@
+// camel-k: dependency=camel-azure-storage-queue
+//
+// Apache Camel Azure Storage Queue Consumer
+//
+
+from('knative:channel/azure-queue')
+        .log('Received: ${body}')
+
+
diff --git a/09-azure-storage-queue-basic/azure-storage-queue-producer.groovy 
b/09-azure-storage-queue-basic/azure-storage-queue-producer.groovy
new file mode 100644
index 0000000..c6d4b5c
--- /dev/null
+++ b/09-azure-storage-queue-basic/azure-storage-queue-producer.groovy
@@ -0,0 +1,11 @@
+// camel-k: dependency=camel-azure-storage-queue
+//
+// Apache Camel Azure Storage Queue Producer
+//
+// This is just a sample producer for Azure that sends messages to an Azure 
storage queue
+
+import static 
org.apache.camel.component.azure.storage.queue.QueueConstants.MESSAGE_TEXT
+
+from('timer:java?period=3000&repeatCount=30')
+        .setHeader(MESSAGE_TEXT, constant('Hello Camel K'))
+        
.to('azure-storage-queue:{{azure.queue.accountName}}/{{azure.queue.queueName}}?accessKey=RAW({{azure.queue.accessKey}})&operation=sendMessage')
\ No newline at end of file
diff --git a/09-azure-storage-queue-basic/azure-storage-queue-source.yaml 
b/09-azure-storage-queue-basic/azure-storage-queue-source.yaml
new file mode 100644
index 0000000..5a405e2
--- /dev/null
+++ b/09-azure-storage-queue-basic/azure-storage-queue-source.yaml
@@ -0,0 +1,31 @@
+#
+# Apache Camel Azure Storage Queue Source
+#
+apiVersion: sources.knative.dev/v1alpha1
+kind: CamelSource
+metadata:
+  name: camel-azure-storage-queue
+spec:
+  source:
+    integration:
+      configuration:
+        - type: secret
+          value: azure-storage-queue
+      dependencies:
+        # Needed for the Azure Storage Queue component
+        - camel:camel-azure-storage-queue
+    flow:
+      from:
+        # On the URI below, the Azure account name named 'camelazure' and 
queue name named 'messages'
+        # can be adjusted to any values suitable in your scenario
+        uri: azure-storage-queue:camelazure/messages
+        parameters:
+          accessKey: "{{azure.queue.accessKey}}"
+
+        steps:
+        - to: "log:received?showAll=true&multiline=true"
+  sink:
+    ref:
+      apiVersion: messaging.knative.dev/v1beta1
+      kind: InMemoryChannel
+      name: azure-queue
diff --git a/09-azure-storage-queue-basic/azure-storage-queue.properties 
b/09-azure-storage-queue-basic/azure-storage-queue.properties
new file mode 100644
index 0000000..8418913
--- /dev/null
+++ b/09-azure-storage-queue-basic/azure-storage-queue.properties
@@ -0,0 +1,3 @@
+azure.queue.accessKey=FillMe
+azure.queue.accountName=FillMe
+azure.queue.queueName=messages
\ No newline at end of file
diff --git a/09-azure-storage-queue-basic/readme.didact.md 
b/09-azure-storage-queue-basic/readme.didact.md
new file mode 100644
index 0000000..c6b0d84
--- /dev/null
+++ b/09-azure-storage-queue-basic/readme.didact.md
@@ -0,0 +1,181 @@
+# Camel Azure Storage Queue Source Basic Example
+
+This example demonstrates how to get started with Camel based Knative sources 
by showing you some of the most important
+features that you should know before trying to develop more complex examples.
+
+You can find more information about Apache Camel and Apache Camel K on the 
[official Camel website](https://camel.apache.org).
+
+## Before you begin
+
+Read the general instructions in the [root README.md file](../README.md) for 
setting up your environment and the Kubernetes cluster before looking at this 
example.
+
+Make sure you've read the [installation 
instructions](https://camel.apache.org/camel-k/latest/installation/installation.html)
 for your specific
+cluster before starting the example.
+
+You should open this file with 
[Didact](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-didact)
 if available on your IDE.
+
+## Requirements
+
+<a href='didact://?commandId=vscode.didact.validateAllRequirements' 
title='Validate all requirements!'><button>Validate all Requirements at 
Once!</button></a>
+
+**Kubectl CLI**
+
+The Kubernetes `kubectl` CLI tool will be used to interact with the Kubernetes 
cluster.
+
+[Check if the Kubectl CLI is 
installed](didact://?commandId=vscode.didact.cliCommandSuccessful&text=kubectl-requirements-status$$kubectl%20help&completion=Checked%20kubectl%20tool%20availability
 "Tests to see if `kubectl help` returns a 0 return code"){.didact}
+
+*Status: unknown*{#kubectl-requirements-status}
+
+**Connection to a Kubernetes cluster**
+
+You need to connect to a Kubernetes cluster in order to run the example.
+
+[Check if you're connected to a Kubernetes 
cluster](didact://?commandId=vscode.didact.cliCommandSuccessful&text=cluster-requirements-status$$kubectl%20get%20pod&completion=Checked%20Kubernetes%20connection
 "Tests to see if `kubectl get pod` returns a 0 return code"){.didact}
+
+*Status: unknown*{#cluster-requirements-status}
+
+**Apache Camel K CLI ("kamel")**
+
+You need the Apache Camel K CLI ("kamel") in order to access all Camel K 
features.
+
+[Check if the Apache Camel K CLI ("kamel") is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=kamel-requirements-status$$kamel%20version$$Camel%20K%20Client&completion=Checked%20if%20Camel%20K%20CLI%20is%20available%20on%20this%20system.
 "Tests to see if `kamel version` returns a result"){.didact}
+
+*Status: unknown*{#kamel-requirements-status}
+
+**Knative installed on the cluster**
+
+The cluster also needs to have Knative installed and working. Refer to the 
[official Knative documentation](https://knative.dev/v0.15-docs/install/) for 
information on how to install it in your cluster.
+
+[Check if the Knative Serving is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=kserving-project-check$$kubectl%20api-resources%20--api-group=serving.knative.dev$$kservice%2Cksvc&completion=Verified%20Knative%20services%20installation.
 "Verifies if Knative Serving is installed"){.didact}
+
+*Status: unknown*{#kserving-project-check}
+
+[Check if the Knative Eventing is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=keventing-project-check$$kubectl%20api-resources%20--api-group=messaging.knative.dev$$inmemorychannels&completion=Verified%20Knative%20eventing%20services%20installation.
 "Verifies if Knative Eventing is installed"){.didact}
+
+*Status: unknown*{#keventing-project-check}
+
+**Knative Camel Source installed on the cluster**
+
+The cluster also needs to have installed the Knative Camel Source from the 
camel.yaml in the [Eventing Sources release 
page](https://github.com/knative/eventing-contrib/releases/tag/v0.15.0)
+
+[Check if the Knative Camel Source is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=kservice-project-check$$kubectl%20api-resources%20--api-group=sources.knative.dev$$camelsources&completion=Verified%20Knative%20Camel%20Source%20installation.
 "Verifies if Knative Camel Source is installed"){.didact}
+
+*Status: unknown*{#kservice-project-check}
+
+### Optional Requirements
+
+The following requirements are optional. They don't prevent the execution of 
the demo, but may make it easier to follow.
+
+**VS Code Extension Pack for Apache Camel**
+
+The VS Code Extension Pack for Apache Camel provides a collection of useful 
tools for Apache Camel K developers,
+such as code completion and integrated lifecycle management. They are 
**recommended** for the tutorial, but they are **not**
+required.
+
+You can install it from the VS Code Extensions marketplace.
+
+[Check if the VS Code Extension Pack for Apache Camel by Red Hat is 
installed](didact://?commandId=vscode.didact.extensionRequirementCheck&text=extension-requirement-status$$redhat.apache-camel-extension-pack&completion=Camel%20extension%20pack%20is%20available%20on%20this%20system.
 "Checks the VS Code workspace to make sure the extension pack is 
installed"){.didact}
+
+*Status: unknown*{#extension-requirement-status}
+
+## 1. Preparing the namespace
+
+Let's open a terminal and go to the example directory:
+
+```
+cd 09-azure-storage-queue-basic
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$cd%2009-azure-storage-queue-basic&completion=Executed%20command.
 "Opens a new terminal and sends the command above"){.didact})
+
+
+We're going to create a namespace named `camel-k-azure-queue-knative` for 
running the example. To create it, execute the following command:
+
+```
+kubectl create namespace camel-k-azure-queue-knative
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20create%20namespace%20camel-k-azure-queue-knative&completion=New%20project%20creation.
 "Opens a new terminal and sends the command above"){.didact})
+
+Now we can set the `camel-k-azure-queue-knative` namespace as default 
namespace for the following commands:
+
+```
+kubectl config set-context --current --namespace=camel-k-azure-queue-knative
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20config%20set-context%20--current%20--namespace%3Dcamel-k-azure-queue-knative&completion=New%20project%20creation.
 "Opens a new terminal and sends the command above"){.didact})
+
+You need to install Camel K in the `camel-k-azure-queue-knative` namespace (or 
globally in the whole cluster).
+In many settings (e.g. OpenShift, CRC), it's sufficient to execute the 
following command to install Camel K:
+
+```
+kamel install
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kamel%20install&completion=Installing%20Camel%20K.
 "Opens a new terminal and sends the command above"){.didact})
+
+NOTE: The `kamel install` command requires some prerequisites to be successful 
in some situations, e.g. you need to enable the registry addon on Minikube. 
Refer to the [Camel K install 
guide](https://camel.apache.org/camel-k/latest/installation/installation.html) 
for cluster-specific instructions.
+
+To check that Camel K is installed we'll retrieve the IntegrationPlatform 
object from the namespace:
+
+```
+kubectl get integrationplatform
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20get%20integrationplatform&completion=Executed%20Command.
 "Opens a new terminal and sends the command above"){.didact})
+
+You should find an IntegrationPlatform in status `Ready`.
+
+You can now proceed to the next section.
+
+## 2. Preparing the environment
+
+This repository contains a simple 
[azure-storage-queue.properties](didact://?commandId=vscode.openFolder&projectFilePath=09-azure-storage-queue-basic/azure-storage-queue.properties&completion=Opened%20the%azure-storage-queue.properties%20file
 "Opens the azure-storage-queue.properties file"){.didact} that contains the 
access key for accessing the Azure Storage Queue containers.
+
+```
+kubectl create secret generic azure-storage-queue 
--from-file=azure-storage-queue.properties
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20create%20secret%20generic%20azure-storage-queue%20--from-file%3Dazure-storage-queue.properties&completion=secret%20%22azure-storage-queue%22%20created.
 "Create a secret with Azure Storage credentials"){.didact})
+
+As the example levareges [Knative Eventing 
channels](https://knative.dev/v0.15-docs/eventing/channels/), we need to create 
the one that the example will use:
+
+```
+kubectl apply -f azure-storage-queue-channel.yaml
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20apply%20-f%20azure-storage-queue-channel.yaml&completion=inmemorychannel.messaging.knative.dev/azure-queue$20created.
 "Create a Knative InMemoryChannel named azure-queue"){.didact})
+
+
+## 2. Running a Camel Source
+
+This repository contains a simple Camel Source based on the [Azure Storage 
Queue Service 
component](https://camel.apache.org/components/latest/azure-storage-queue-component.html)
 that forward messages events received on the Azure Queue container orders to a 
Knative channel named `azure-queue`.
+
+Use the following command to deploy the Camel Source:
+
+```
+kubectl apply -f azure-storage-queue-source.yaml
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20apply%20-f%20azure-storage-queue-source.yaml&completion=camelsource.sources.knative.dev/camel-azure-storage-queue%20created.
 "Opens a new terminal and sends the command above"){.didact})
+
+## 2. Running a basic integration to create Azure Storage Queue for 
consumption by the Camel Source
+
+You need a producer sending messages to `messages` Azure Storage Queue to try 
this example. This integration
+comes with a sample producer that will send messages with the text `Hello 
Camel K` every 3 seconds.
+
+```
+kamel run --secret azure-storage-queue azure-storage-queue-producer.groovy
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kamel%20run%20--secret%20azure-storage-queue%20azure-storage-queue-producer.groovy&completion=Camel%20K%20azure-storage-queue-producer%20integration%20run%20in%20dev%20mode.
 "Opens a new terminal and sends the command above"){.didact})
+
+If everything is ok, after the build phase finishes, you should see the Camel 
integration running.
+
+## 3. Running a basic integration 
+```
+kamel run azure-storage-queue-consumer.groovy --dev --secret 
azure-storage-queue
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kamel%20run%20azure-storage-queue-consumer.groovy%20--dev%20--secret%20azure-storage-queue&completion=Camel%20K%20azure-storage-queue-consumer%20integration%20run%20in%20dev%20mode.
 "Opens a new terminal and sends the command above"){.didact})
+
+If everything is ok, after the build phase finishes, you should see the Camel 
integration running.
+
+
+## 4. Uninstall
+
+To cleanup everything, execute the following command:
+
+```kubectl delete namespace camel-k-azure-queue-knative```
+
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20delete%20namespace%20camel-k-azure-queue-knative&completion=Removed%20the%20namespace%20from%20the%20cluster.
 "Cleans up the cluster after running the example"){.didact})
diff --git a/09-azure-storage-queue-basic/readme.md 
b/09-azure-storage-queue-basic/readme.md
new file mode 100644
index 0000000..c6b0d84
--- /dev/null
+++ b/09-azure-storage-queue-basic/readme.md
@@ -0,0 +1,181 @@
+# Camel Azure Storage Queue Source Basic Example
+
+This example demonstrates how to get started with Camel based Knative sources 
by showing you some of the most important
+features that you should know before trying to develop more complex examples.
+
+You can find more information about Apache Camel and Apache Camel K on the 
[official Camel website](https://camel.apache.org).
+
+## Before you begin
+
+Read the general instructions in the [root README.md file](../README.md) for 
setting up your environment and the Kubernetes cluster before looking at this 
example.
+
+Make sure you've read the [installation 
instructions](https://camel.apache.org/camel-k/latest/installation/installation.html)
 for your specific
+cluster before starting the example.
+
+You should open this file with 
[Didact](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-didact)
 if available on your IDE.
+
+## Requirements
+
+<a href='didact://?commandId=vscode.didact.validateAllRequirements' 
title='Validate all requirements!'><button>Validate all Requirements at 
Once!</button></a>
+
+**Kubectl CLI**
+
+The Kubernetes `kubectl` CLI tool will be used to interact with the Kubernetes 
cluster.
+
+[Check if the Kubectl CLI is 
installed](didact://?commandId=vscode.didact.cliCommandSuccessful&text=kubectl-requirements-status$$kubectl%20help&completion=Checked%20kubectl%20tool%20availability
 "Tests to see if `kubectl help` returns a 0 return code"){.didact}
+
+*Status: unknown*{#kubectl-requirements-status}
+
+**Connection to a Kubernetes cluster**
+
+You need to connect to a Kubernetes cluster in order to run the example.
+
+[Check if you're connected to a Kubernetes 
cluster](didact://?commandId=vscode.didact.cliCommandSuccessful&text=cluster-requirements-status$$kubectl%20get%20pod&completion=Checked%20Kubernetes%20connection
 "Tests to see if `kubectl get pod` returns a 0 return code"){.didact}
+
+*Status: unknown*{#cluster-requirements-status}
+
+**Apache Camel K CLI ("kamel")**
+
+You need the Apache Camel K CLI ("kamel") in order to access all Camel K 
features.
+
+[Check if the Apache Camel K CLI ("kamel") is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=kamel-requirements-status$$kamel%20version$$Camel%20K%20Client&completion=Checked%20if%20Camel%20K%20CLI%20is%20available%20on%20this%20system.
 "Tests to see if `kamel version` returns a result"){.didact}
+
+*Status: unknown*{#kamel-requirements-status}
+
+**Knative installed on the cluster**
+
+The cluster also needs to have Knative installed and working. Refer to the 
[official Knative documentation](https://knative.dev/v0.15-docs/install/) for 
information on how to install it in your cluster.
+
+[Check if the Knative Serving is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=kserving-project-check$$kubectl%20api-resources%20--api-group=serving.knative.dev$$kservice%2Cksvc&completion=Verified%20Knative%20services%20installation.
 "Verifies if Knative Serving is installed"){.didact}
+
+*Status: unknown*{#kserving-project-check}
+
+[Check if the Knative Eventing is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=keventing-project-check$$kubectl%20api-resources%20--api-group=messaging.knative.dev$$inmemorychannels&completion=Verified%20Knative%20eventing%20services%20installation.
 "Verifies if Knative Eventing is installed"){.didact}
+
+*Status: unknown*{#keventing-project-check}
+
+**Knative Camel Source installed on the cluster**
+
+The cluster also needs to have installed the Knative Camel Source from the 
camel.yaml in the [Eventing Sources release 
page](https://github.com/knative/eventing-contrib/releases/tag/v0.15.0)
+
+[Check if the Knative Camel Source is 
installed](didact://?commandId=vscode.didact.requirementCheck&text=kservice-project-check$$kubectl%20api-resources%20--api-group=sources.knative.dev$$camelsources&completion=Verified%20Knative%20Camel%20Source%20installation.
 "Verifies if Knative Camel Source is installed"){.didact}
+
+*Status: unknown*{#kservice-project-check}
+
+### Optional Requirements
+
+The following requirements are optional. They don't prevent the execution of 
the demo, but may make it easier to follow.
+
+**VS Code Extension Pack for Apache Camel**
+
+The VS Code Extension Pack for Apache Camel provides a collection of useful 
tools for Apache Camel K developers,
+such as code completion and integrated lifecycle management. They are 
**recommended** for the tutorial, but they are **not**
+required.
+
+You can install it from the VS Code Extensions marketplace.
+
+[Check if the VS Code Extension Pack for Apache Camel by Red Hat is 
installed](didact://?commandId=vscode.didact.extensionRequirementCheck&text=extension-requirement-status$$redhat.apache-camel-extension-pack&completion=Camel%20extension%20pack%20is%20available%20on%20this%20system.
 "Checks the VS Code workspace to make sure the extension pack is 
installed"){.didact}
+
+*Status: unknown*{#extension-requirement-status}
+
+## 1. Preparing the namespace
+
+Let's open a terminal and go to the example directory:
+
+```
+cd 09-azure-storage-queue-basic
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$cd%2009-azure-storage-queue-basic&completion=Executed%20command.
 "Opens a new terminal and sends the command above"){.didact})
+
+
+We're going to create a namespace named `camel-k-azure-queue-knative` for 
running the example. To create it, execute the following command:
+
+```
+kubectl create namespace camel-k-azure-queue-knative
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20create%20namespace%20camel-k-azure-queue-knative&completion=New%20project%20creation.
 "Opens a new terminal and sends the command above"){.didact})
+
+Now we can set the `camel-k-azure-queue-knative` namespace as default 
namespace for the following commands:
+
+```
+kubectl config set-context --current --namespace=camel-k-azure-queue-knative
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20config%20set-context%20--current%20--namespace%3Dcamel-k-azure-queue-knative&completion=New%20project%20creation.
 "Opens a new terminal and sends the command above"){.didact})
+
+You need to install Camel K in the `camel-k-azure-queue-knative` namespace (or 
globally in the whole cluster).
+In many settings (e.g. OpenShift, CRC), it's sufficient to execute the 
following command to install Camel K:
+
+```
+kamel install
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kamel%20install&completion=Installing%20Camel%20K.
 "Opens a new terminal and sends the command above"){.didact})
+
+NOTE: The `kamel install` command requires some prerequisites to be successful 
in some situations, e.g. you need to enable the registry addon on Minikube. 
Refer to the [Camel K install 
guide](https://camel.apache.org/camel-k/latest/installation/installation.html) 
for cluster-specific instructions.
+
+To check that Camel K is installed we'll retrieve the IntegrationPlatform 
object from the namespace:
+
+```
+kubectl get integrationplatform
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20get%20integrationplatform&completion=Executed%20Command.
 "Opens a new terminal and sends the command above"){.didact})
+
+You should find an IntegrationPlatform in status `Ready`.
+
+You can now proceed to the next section.
+
+## 2. Preparing the environment
+
+This repository contains a simple 
[azure-storage-queue.properties](didact://?commandId=vscode.openFolder&projectFilePath=09-azure-storage-queue-basic/azure-storage-queue.properties&completion=Opened%20the%azure-storage-queue.properties%20file
 "Opens the azure-storage-queue.properties file"){.didact} that contains the 
access key for accessing the Azure Storage Queue containers.
+
+```
+kubectl create secret generic azure-storage-queue 
--from-file=azure-storage-queue.properties
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20create%20secret%20generic%20azure-storage-queue%20--from-file%3Dazure-storage-queue.properties&completion=secret%20%22azure-storage-queue%22%20created.
 "Create a secret with Azure Storage credentials"){.didact})
+
+As the example levareges [Knative Eventing 
channels](https://knative.dev/v0.15-docs/eventing/channels/), we need to create 
the one that the example will use:
+
+```
+kubectl apply -f azure-storage-queue-channel.yaml
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20apply%20-f%20azure-storage-queue-channel.yaml&completion=inmemorychannel.messaging.knative.dev/azure-queue$20created.
 "Create a Knative InMemoryChannel named azure-queue"){.didact})
+
+
+## 2. Running a Camel Source
+
+This repository contains a simple Camel Source based on the [Azure Storage 
Queue Service 
component](https://camel.apache.org/components/latest/azure-storage-queue-component.html)
 that forward messages events received on the Azure Queue container orders to a 
Knative channel named `azure-queue`.
+
+Use the following command to deploy the Camel Source:
+
+```
+kubectl apply -f azure-storage-queue-source.yaml
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20apply%20-f%20azure-storage-queue-source.yaml&completion=camelsource.sources.knative.dev/camel-azure-storage-queue%20created.
 "Opens a new terminal and sends the command above"){.didact})
+
+## 2. Running a basic integration to create Azure Storage Queue for 
consumption by the Camel Source
+
+You need a producer sending messages to `messages` Azure Storage Queue to try 
this example. This integration
+comes with a sample producer that will send messages with the text `Hello 
Camel K` every 3 seconds.
+
+```
+kamel run --secret azure-storage-queue azure-storage-queue-producer.groovy
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kamel%20run%20--secret%20azure-storage-queue%20azure-storage-queue-producer.groovy&completion=Camel%20K%20azure-storage-queue-producer%20integration%20run%20in%20dev%20mode.
 "Opens a new terminal and sends the command above"){.didact})
+
+If everything is ok, after the build phase finishes, you should see the Camel 
integration running.
+
+## 3. Running a basic integration 
+```
+kamel run azure-storage-queue-consumer.groovy --dev --secret 
azure-storage-queue
+```
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kamel%20run%20azure-storage-queue-consumer.groovy%20--dev%20--secret%20azure-storage-queue&completion=Camel%20K%20azure-storage-queue-consumer%20integration%20run%20in%20dev%20mode.
 "Opens a new terminal and sends the command above"){.didact})
+
+If everything is ok, after the build phase finishes, you should see the Camel 
integration running.
+
+
+## 4. Uninstall
+
+To cleanup everything, execute the following command:
+
+```kubectl delete namespace camel-k-azure-queue-knative```
+
+([^ 
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20delete%20namespace%20camel-k-azure-queue-knative&completion=Removed%20the%20namespace%20from%20the%20cluster.
 "Cleans up the cluster after running the example"){.didact})

Reply via email to