StreamNative Hub is an online service for finding, reviewing, and downloading extensions for the Apache Pulsar ecosystem. It highlights features, richer component descriptions, links to external resources for the components, and installation and support information.

The StreamNative Hub currently hosts the following extensions for Pulsar ecosystem.

• Connectors (source & sink)
• Offloaders
• Protocol handlers
• Authentication plugins
• Integrations with data processing engines
• Interceptors
• ... and more

If a new plugin is introduced, you should upload the plugin to the target category. Currently, the StreamNative supports the following categories for the plugin.

• Authentication
• Connector
• Data processing
• Deployment
• Handler
• Logging
• Monitoring
• Offloader

If a new category is required, you can create it. For details about how to create a new category, see create new category.

This section describes operations to be performed before creating a PR (Pull Request) for a plugin.

• Clone the pulsar-hub repository to the local.
• Create a sub-folder under the cloned pulsar-hub repository and put the document in this sub-folder. The sub-folder name is set to the version of the plugin to be submitted, such as 2.5.1.
• Put the plugin image in the image folder under the cloned pulsar-hub repository.

To create a new category, follow these steps:

1. Create a branch based on the latest pulsar-hub master repository.
2. Create a sub-folder under the pulsar-hub folder in the local. Set the name of the sub-folder to the category name with lower cases. If the category name consists of multiple words, use the hyphen (-) between these words, such as data-processing.

To create a document for a new plugin, follow these steps:

1. Create a branch based on the latest pulsar-hub master repository.
2. Create a document in the target folder for the plugin. For the document template about the plugin, see plugin document template.
3. Commit your updates, create a PR, and then publish the PR to the pulsar-hub master repository.
4. Update comments, if any.
5. If no more comment, ask reviewers to approve the PR and merge the PR to the master.

This section describes a plugin document structure, including the following two parts:

• Metadata
• Body text

The metadata of a plugin consists of the following fields:

description:
author: 
contributors: 
language: 
document:
source: 
license: 
tags: 
alias: 
features:
license_link: 
icon: 
download: 
support:
support_link:
support_image:
dockerfile:
owner_name:
owner_img:
id: 

The following table describes tags covered in the metadata of a plugin.

In general, the body text of a plugin document includes the following sections:

• Overview
• Installation
  • Prerequisites
  • Procedures
• Configuration
  • XXX configuration (XXX refers to the plugin name.)
  • Configure XXX (XXX refers to the plugin name.)
• Usage
• Monitoring (Optional)
• Security (Optional)
• Metrics (Optional)
• How it works (Optional)
• Reference (Optional)
• Troubleshooting (Optional)
• Tutorial (Optional)

### Overview

> Describe what the plugin is used for.

### Installation

> Describe how to install or load the plugin.

#### Prerequisites

> List prerequisite used for installing the plugin, if any.

#### Procedures

> Lists how to instal the plugin.

### Configuration

> List some configuration examples to describe what the plugin can be used to do.

#### XXX configuration

> List configuration items available for the plugin. XXX refers to the plugin name.

#### Configure XXX

> How to configure the plugin through Json or Yaml file. XXX refers to the plugin name.

### Usage

> Provide an example to describe what the connector can be used to do.

### Monitoring (Optional)

> Describe how to monitor the plugin.

### Security (Optional)

> List security configurations required to be configured and how to configure it.

### Metrics (Optional)

> List metrics available for the plugin.

### How it works (Optional)

> List basic principles for the plugin to work.

### Reference (Optional)

> List additional external references, if any.

### Troubleshooting (Optional)

> List FAQs and how to troubleshoot the bugs, if any.

### Tutorial (Optional)

> List a step-by-step for the whole process.