Add Stitch support to plugins
Custom or community plugins that want to support the transform of artifacts using Stitch rules, must call the Stitch Engine transformer.
Custom or community plugins that want to support the transform of artifacts using Stitch rules, must call the Stitch Engine transformer.
Stitch is a new capability of digital.ai Deploy that provides a declarative way to customize configuration files for deployments of bespoke applications and commercial of the shelf components (COTS). It is designed for the world of cloud and containers, and builds on top of Deploy concepts of UDM model, types, rules engine and plugins.
This tutorial will teach you how to use Stitch capability of Digital.ai Deploy, when deploying to a Kubernetes cluster. For more information about Stitch, please see Introduction to Stitch.
This topic covers plugin synchronization, which involves aligning the filesystem and database during system startup to streamline the plugin management process.
The following table lists the plugins supported by different versions of Deploy.
When user wants to generate additional documents based on the content of the deployment plugin uses preprocessing or postprocessing stitch transformation. Preprocessing should be used if generated documents should go through regular stitch transformations and postprocessing should be used when no additional transformation is expected.
The upcoming version of Digital.ai Deploy 24.1 requires upgrading to Java 17 as it is the next Long Term Support (LTS) version of the JDK. This ensures that Deploy has access to the latest Java functionalities and as well as up to date security fixes.