Digital.ai Deploy 10.3.x Release Notes

Upgrade instructions

The Digital.ai Deploy upgrade process you use depends on the version from which you are upgrading, and the version to which you want to go.

For detailed instructions based on your upgrade scenario, refer to Upgrade Deploy.

In addition, you must consider the following new features that are part of Deploy 10.3.2 as you plan your installation or upgrade.

Support Policy

Product versions are now supported for one year following their release, with an additional three months after the end of that year available to ask questions of support. For more information, refer to Digital.ai Support Policy.

Digital.ai Deploy 10.3.2

In addition to bug fixes, the Digital.ai Deploy 10.3.2 includes the following new features:

Permission microservice (BETA)
Central Configuration Management as a standalone microservice
Enhanced Kubernetes Operator-based installer
Plugin Manager APIs
Internet Explorer 11 support—end-of-life
Support for PostgreSQL 13.4
Updates to Deploy Plugins

Permission microservice (BETA)

The Digital.ai Deploy's Permission service—by default—runs (embedded) on the Digital.ai Deploy server.
One of the best practices is to run the Permission service with its own (separate) database schema in order to separate the connection pools from the Deploy's database schema.
Use the centralConfiguration/deploy-permission-service.yaml file to define the Permission service's database configuration if you want to have the Permissions data stored in a separate database.
You can also customize your Deploy installation or upgrade to have the Permission microservice installed on a separate server, if required. This feature is BETA in Deploy 10.3 and is not recommended for use in production setup.

Note:

The Operator-based installer for Deploy has no support to install the Permissions microservice on a standalone server. If you use the Operator-based installer to install Deploy, go through the Operator-based installation process to install Deploy first and follow the instructions here to install the Permissions microservice on a separate server.
There is no separate Docker image available for installing the Permissions microservice on a standalone server.

For more information, see Permission microservice

Central Configuration

In Digital.ai Deploy 10.3.2, you can run the Central Configuration as a standalone service. You can now run the Central Configuration as a separate service if you have a setup with multiple Deploy servers with external workers configured on your system.
The Central Configuration service is installed on the Deploy server as an embedded service by default. You can choose to run the Central Configuration as a separate or embedded service.
Are you upgrading from Deploy 10.1 or later to 10.3?
- If you are upgrading from Deploy 10.1 or later to 10.3 and if you want to run Central Configuration on a separate server, you must manually copy the centralConfiguration directory from the Deploy server to the newly configured Central Configuration server. For more information, see Install Central Configuration as a separate microservice.

For more information, see Central Configuration

Enhancements to Deploy's encryption policy

The following alpha-numeric and special characters are used when Deploy encrypts sensitive information such as passwords.

Uppercase letters (A–Z)
Lowercase letters (a–z)
Numbers (0–9)
Special characters (~`!@#%^&*()-_=+[{]}|;:'",<.>/?")

Kubernetes Operator-based Installation

With Deploy 10.3.2, the Kubernetes Operator-based installer offers the following enhancements:

Kubernetes Operator supports installation of Digital.ai Deploy on Kubernetes On-premise cluster and OpenShift VMWare vSphere clusters
With upgrade to Digital.ai Deploy 10.3.2, you can migrate the previous Helm-based installation (Deploy 10.1) to Operator-based installation on Kubernetes On-premise and OpenShift VMWare vSphere clusters.

For more information, see:

Plugin Manager and Plugin Manager CLI

REST API docs for the Plugin Manager have been published to allow non-interactive installation and upgrade of Deploy plugins.

No support for Internet Explorer 11

Internet Explorer 11 is no longer supported by Digital.ai Deploy 10.3 and later.

Support for PostgreSQL 13.4

In addition to other supported PostgreSQL versions as listed in Deploy System Requirements, Digital.ai Deploy 10.3.2 supports PostgreSQL 13.4.

Plugins

JBoss plugin

Digital.ai Deploy 10.3 JBoss plugin introduces the following new functionalities.

Add / delete in “/subsystem="batch-jberet", See Deploy a batch application.
Add / delete system properties, See Deploy System Properties.
Add / delete extensions (“/extension”), See Configure JBoss Extension.

Google Cloud Compute plugin

Implemented IAM Token Generation for Digital.ai Deploy Google Cloud Compute Plugin. You can use this feature to generate IAM token for authentication using Overthere connection. See Generate IAM Token.
Digital.ai introduces Token based authentication for GCP using Overthere connection. See Service Account Token Gcp Credentials.

HashiCorp Vault Plugin

Digital.ai introduces Namespace functionality in Hashicorp Vault plugin. You can use this functionality to store and retrieve secrets based on namespace.

Bug fixes

Bug fixes—10.3.2

[ENG-1998] - Modified the Deployment Mapping screen message.
[ENG-2022] - Fix made to ensure multiple updates to the same CI will pick the latest key and token from the previous update for WAS Plugin.
[ENG-4296] - Fixed the deployment packages sorting issue.
[ENG-6934] - Fixed the Force Redeploy issue that breaks the deployment rollback feature.
[ENG-8081] - Fixed the Worker Retry Connection failure issue.
[ENG-7400] - Fixed the "Failed to Deserialize Payload" error in Deploy 10.3 GUI.
[ENG-7800] - Fixed the deployment issue in Deploy 10.2.4.
[ENG-7980] - Fixed the broken Jython patch for issues 2618 and 2894.
[FI-744] - Fixed the issue where XL-deploy failed when configured to start the JMX.
[FI-798] - Fixed the issue where the upgrade to 10.2.2 Directory reference updates cannot be applied.
[FI-800] - Fixed the placeholders issue where the empty folders are deleted.
[FI-813] - Fixed the Deploy application unresponsiveness caused by session timeout.
[FI-829] - Fixed the "Cannot be cast error" when upgrading XLD from 9.5.3 to 10.2.2.