impl/

directory
v4.4.4 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Jul 19, 2022 License: MIT

README

Implementations

This is an internal package containing the implementations of Benthos component types (inputs, processors, outputs, etc) organised into sub categories.

If you intend to create a new component type then use the docs at https://pkg.go.dev/github.com/utilitywarehouse/data-infra-benthos/v4/public/service, and there are some implementations that might be worth using as a reference:

Directories

Path Synopsis
Package amqp1 will eventually contain all implementations of AMQP 1 components (that are currently within ./internal/old)
Package amqp1 will eventually contain all implementations of AMQP 1 components (that are currently within ./internal/old)
shared
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
aws
Package azure will eventually contain all implementations of Azure components (that are currently within ./internal/old)
Package azure will eventually contain all implementations of Azure components (that are currently within ./internal/old)
shared
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
aws
Package io contains component implementations that have a small dependency footprint (mostly standard library) and interact with external systems via the filesystem and/or network sockets.
Package io contains component implementations that have a small dependency footprint (mostly standard library) and interact with external systems via the filesystem and/or network sockets.
aws
Package mqtt will eventually contain all implementations of MQTT components (that are currently within ./internal/old)
Package mqtt will eventually contain all implementations of MQTT components (that are currently within ./internal/old)
shared
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
Package pure contains all component implementations that are pure, in that they do not interact with external systems.
Package pure contains all component implementations that are pure, in that they do not interact with external systems.
old
Package sftp will eventually contain all implementations of SFTP components (that are currently within ./internal/old)
Package sftp will eventually contain all implementations of SFTP components (that are currently within ./internal/old)
shared
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
Package shared contains docs fields that need to be shared across old and new component implementations, it needs to be separate from the parent package in order to avoid circular dependencies (for now).
Package xml is a temporary way to convert XML to JSON.
Package xml is a temporary way to convert XML to JSON.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL