Azure IoT Operations connector metadata
8.0-previewSchema URL
Schema that defines how to write a connector metadata document when writing connectors for Azure IoT Operations solutions
Properties
The name of the connector.
The version of this connector. This must use semantic versioning such as '1.2.3'
The container image details for this connector image.
The CPU architectures that this connector image was built for. At least one must be specified.
The array of inbound endpoints in a device that this connector will be deployed for.
The address of the AIO connector metadata schema that this connector metadata file adheres to.
A brief (human-readable) description of the connector (preferably in English). This is seen when browsing connectors in the portal.
True if this connector is considered a preview version.
A name and/or email of the maintainer of this connector.
A name and/or email of the vendor that distributes this connector.
The array of secrets that are required for the connector application to work. The secret will be mounted onto all connector instances deployed for this connector application
The array of storage volumes that are required for the connector application to work.
Details about the source code that compiled this connector
3 nested properties
The programming language used to write this connector
The version of the programming language used to write this connector
Details about the versions of the AIO SDKs used to write this connector (if they were used)
4 nested properties
The version of the Azure IoT Operations MQTT package
The version of the Azure IoT Operations protocol package
The version of the Azure IoT Operations services package
The version of the Azure IoT Operations connector package
The AIO requirements to run this connector
2 nested properties
The minimal (inclusive) version that can run this connector.
The maximal (inclusive) version that can run this connector. If there is no known exact version, wildcards can be used such as '1..'. Alternatively, not specifying an aioMaxVersion signals no upper bound
The array of keys in the connector configuration
The alternative name of this type. For example, OPC UA knows "datapoints" as "tags"
2 nested properties
The singular form of the name of this type
The plural form of the name of this type
If true, inbound endpoints are enabled by default. Users may still specify in the deployed device definition if each endpoint is enabled or not and that value will override this value.
The recommended configuration to use for allocating device inbound endpoints for the connector instances. Only 'bucketized' is currently supported.
The recommended number of replicas to deploy for this connector.
Definitions
Describes the limits to this model type that this connector supports. For instance, a connector may support between 0 to 5 datasets.
The maximum number of this model type that this connector supports. If not specified, the default is whatever limits the ADR service itself has.
The minimum number of this model type that this connector supports.
The specific default values that will be used by the connector when publishing telemetry to the MQTT broker.
The default MQTT topic that will be published to. Values are allowed to contain deploy-time parameters like 'mqtt/{deviceName}/{inboundEndpointName}/myMessages'. The supported parameter tokens are: {deviceName}, {inboundEndpointName}, {assetName}, {datasetName}, {eventName}, {streamName}, and {kubernetesNamespace}. Dataset/event/stream name tokens are only allowed if the configured destination is for a dataset/event/stream.
The default MQTT quality of service that MQTT messages will be published with
The default time to live that MQTT messages will be published with.
The default retain flag value that MQTT messages will be published with.
The broker state store-specific default values that will be used by the connector if not otherwise specified.
The default broker state store key that will be published to. Values are allowed to contain deploy-time parameters like 'dss/{deviceName}/{inboundEndpointName}'. The supported parameter tokens are: {deviceName}, {inboundEndpointName}, {assetName}, {datasetName}, {eventName}, {streamName}, and {kubernetesNamespace}. Dataset/event/stream name tokens are only allowed if the configured destination is for a dataset/event/stream.
The storage-specific default values that will be used by the connector if not otherwise specified.
The default path that storage will use. Values are allowed to contain deploy-time parameters like 'storage/{deviceName}/{inboundEndpointName}'. The supported parameter tokens are: {deviceName}, {inboundEndpointName}, {assetName}, {datasetName}, {eventName}, {streamName}, and {kubernetesNamespace}. Dataset/event/stream name tokens are only allowed if the configured destination is for a dataset/event/stream.
The alternative name of this type. For example, OPC UA knows "datapoints" as "tags"
The singular form of the name of this type
The plural form of the name of this type
Details about if a field is required or not and what shape its value should take
If this field is relevant to this connector or not. If required, the connector cannot function without this field being provided in the specified shape. If unsupported, the connector will ignore any value provided for this field. If optional, the connector can function with or without this field being provided, but the behavior may vary depending on it.
The set of regex that this field's value should adhere to.
An example value for this field that fits the expected format
Additional user-readable context for this field. May explain how the field is used or explain the validation rules around it.