Save notifications

In some use cases it may be useful to inform third party services after a collection has been saved - e.g. to propagate metadata changes to another backend system.

Fusion allows configuring a REST endpoint that will be notified after saving changes.

Message format

Changes are propagated by a REST POST request containing information about the changes that have just been made.

The message format is as follows:

{
  "oldCollection" : { ... },    // old collection as json
  "newCollection" : { ... }     // new collection as json
}

Configuration

In addition to the endpoint URL, a whitelist of collection types can be specified in the configuration in order to support save notifications only for a subset of collection types. If the whitelist is empty, notification takes place for all collection types.

The feedback request can be secured using user authentication, basic authentication or a static bearer token.

Configure via Helm values:

organizer:
  saveNotification:
    enabled: false
    url:
    typeIdsWhitelist: ['generic']
    auth:
      userAuth:
        enabled: false
      basicAuthenticated:
        enabled: false
      bearerAuthenticated:
        enabled: false

secrets:
  saveNotification:
    username:
    password:
    bearerToken:

Authentication Methods

User Authentication: organizer.saveNotification.auth.userAuth.enabled: true

Basic Authentication: Set organizer.saveNotification.auth.basicAuthenticated.enabled: true and provide credentials in secrets.saveNotification.username and secrets.saveNotification.password

Bearer Token: Set organizer.saveNotification.auth.bearerAuthenticated.enabled: true and provide token in secrets.saveNotification.bearerToken

Choose one of these methods or omit all to disable authentication.

For detailed information about sealed secrets, please refer to the Sealed Secrets documentation.