17 docs tagged with "stitch"

Custom or community plugins that want to support the transform of artifacts using Stitch rules, must call the Stitch Engine transformer.

Branches

Implementing custom input/output formats

Stitch is a collection of tools available out-of-the-box with Deploy. Stitch extends Deploy’s capability and enables the field experts in your organization to define and build scaled customizations and variants of reusable deployment patterns that your cloud-native teams can effortlessly consume for their cloud and container deployments.

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.

In order for Deploy to apply any Stitch transformation, the plugin needs to have a support for Stitch since it controls the content in it.

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.

Stitch sources are created under the Configuration tab of the CI Explorer. Using configuration or folder permissions, you can show/hide Stitch sources. As a Stitch source is also a CI, it has the same logic for permissions as all other CI’s.

Stitch macros are reusable building blocks which group the common processors used inside of Stitch rules.

Some of the Stitch features, like preview or dry run, can be run through either Jython or XL CLI.

When you use the Preview option of the deployment plan, you can also see the Stitch preview for it, by using the toggle button to switch between two views. After clicking on the Stitch preview toggle, you can also browse and view Stitch invocation details.

A Stitch processor is a part of a Stitch rule that is responsible for modifying the application's resource configuration files during the deployment planning phase. Processors are defined in a Stitch YAML file in the processor array.

A Stitch repository is a source of rules and macros YAML files, and their associated content. A repository can be any Git repository or a local folder that contains a valid Stitch YAML file. When a Stitch source is added to the configuration, Deploy scans the whole repository or the folder structure recursively, drilling down the folder structure attempting to find valid definitions of Stitch YAML rules. It will look for files with the stitch-rules prefix, and a yaml or yml suffix (e.g. stitch-rules.yaml or stitch-rules-k8s-labels.yaml).

A Stitch rule is a customization rule that can either transform the content of the provided configuration file or generate it. A rule comprises of conditions (the 'when') and processors (the 'how').

The Stitch Workbench is a part of Deploy's web-based user interface that provides an overview of all customizations known to Stitch.

In Stitch, there is additional logging available that you can use for troubleshooting when something goes wrong.