ocm-pubsub

Description#

An OCM repository can be configured to propagate change events via a publish/subscribe system, if there is a persistence provider for the dedicated repository type. If available any known publish/subscribe system can be configured with ocm set pubsub and shown with ocm get pubsub. Hereby, the pub/sub system is described by a typed specification.

The following list describes the supported publish/subscribe system types, their specification versions, and formats:

• PubSub type compound

  A pub/sub system forwarding events to described sub-level systems.

  The following versions are supported:

  • Version v1

    It is described by the following field:

    • specifications list of pubsub specs

      A list of nested sub-level specifications the events should be forwarded to.

• PubSub type redis

  a redis pubsub system.

  The following versions are supported:

  • Version v1

    It is describe by the following field:

    • serverAddr Address of redis server

    • channel pubsub channel

    • database database number

      Publishing using the redis pubsub API. For every change a string message with the format : is published. If multiple repositories should be used, each repository should be configured with a different channel.

There are persistence providers for the following repository types:

• OCIRegistry

See Also#