Clone Binary Sync

This extension was built to enrich stage- and test-systems that run a clone of the productive database, but without its binaries (to conserve space), with a defined subset of binaries from the prod system as a new version.

It assumes that the asset IDs are the same on both systems.

Requirements

• The productive system needs to have CELUM's remote-sdk
• The cloned test server runs this plugin

Usage

The plugin appears as a system task under the "Import" section.

Properties

To be configured in {home}/appserver/conf/custom.properties

cloneBinarySync.license

type: String, required: yes, default: -

The license key for the plugin (product: cloneBinarySync), provided by brix.

cloneBinarySync.search

type: String, required: yes, default: -

An arbitrary Search Util-expression defining which assets should be enriched.

cloneBinarySync.serverUrl

type: String, required: yes, default: -

The remote SDK endpoint to use, e.g. http://celum.server:8765/api

cloneBinarySync.serverSecret

type: String, required: yes, default: -

The server secret you configured in prod's remote.yml

cloneBinarySync.clientId

type: String, required: yes, default: -

The client ID you configured in prod's remote.yml, e.g. clonebinarysync

cloneBinarySync.clientSecret

type: String, required: yes, default: -

The client secret you configured in prod's remote.yml

cloneBinarySync.skipOnNewerVersion

type: String, required: no, default: true

Check if the local asset version is already higher than the remote one, and skip it (assuming it has already been binary-synced)

cloneBinarySync.cronExpression

type: String, required: no, default: -

A Quartz cron expression for automating the task. This is not recommended, and only works when skipOnNewerVersion is true (otherwise it's gonna fill up your disk real fast).

Compatibility Matrix

Release Notes

1.0

Release: 2022-02-14

Initial Version

1.1

Release: 2022-02-25

Added skipOnNewerVersion and cronExpression