Adobe I/O Events - Azure Service Bus connector

This is a sample I/O Events consumer, built using Adobe App Builder, that forwards all incoming events to Azure Service Bus. This sample consumer application can be used as a reference to connect Adobe I/O Events with enterprise's Azure Service Bus.

Setup

• Populate the .env file in the project root and fill it as shown below
• Populate AIO_RUNTIME_NAMESPACE in src/dx-excshell-1/web-src/src/config.json

Usage

• Create subscription in to the Azure Service Bus topic by following these steps - https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal.

• Deploy the app locally or on Adobe's infrastructure using the steps mentioned in the subsequent sections.

• From the UI, configure the Azure Service Bus connection string and topic.

• Now create an event-registration using the runtime-action (from this app) as an event-consumer. All events delivered by I/O Events to this action will get forwarded to the configured Azure Service Bus topic.

Local Dev

• aio app run to start your local Dev server
• App will run on localhost:9080 by default

By default the UI will be served locally but actions will be deployed and served from Adobe I/O Runtime. To start a local serverless stack and also run your actions locally use the aio app run --local option.

Test & Coverage

• Run aio app test to run unit tests for ui and actions
• Run aio app test -e to run e2e tests

Deploy & Cleanup

• aio app deploy to build and deploy all actions on Runtime and static files to CDN
• aio app undeploy to undeploy the app

Config

.env

# This file must not be committed to source control

## please provide your Adobe I/O Runtime credentials
# AIO_RUNTIME_AUTH=
# AIO_RUNTIME_NAMESPACE=

manifest.yml

• List your backend actions under the actions field within the __APP_PACKAGE__ package placeholder. We will take care of replacing the package name placeholder by your project name and version.
• For each action, use the function field to indicate the path to the action code.
• More documentation for supported action fields can be found here.

Action Dependencies

• You have two options to resolve your actions' dependencies:

  1. Packaged action file: Add your action's dependencies to the root package.json and install them using npm install. Then set the function field in manifest.yml to point to the entry file of your action folder. We will use parcelJS to package your code and dependencies into a single minified js file. The action will then be deployed as a single file. Use this method if you want to reduce the size of your actions.

  2. Zipped action folder: In the folder containing the action code add a package.json with the action's dependencies. Then set the function field in manifest.yml to point to the folder of that action. We will install the required dependencies within that directory and zip the folder before deploying it as a zipped action. Use this method if you want to keep your action's dependencies separated.

Debugging in VS Code

While running your local server (aio app run), both UI and actions can be debugged, to do so open the vscode debugger and select the debugging configuration called WebAndActions. Alternatively, there are also debug configs for only UI and each separate action.

Typescript support for UI

To use typescript use .tsx extension for react components and add a tsconfig.json and make sure you have the below config added

 {
  "compilerOptions": {
      "jsx": "react"
    }
  }