Digital.ai Deploy 22.3.x Release Notes

Digital.ai Deploy 22.3.0

Digital.ai Deploy 22.3.0 includes the following new features:

  • System Information tab enhancements
  • Changes to the deploy-cluster.yaml and deployit.conf files—HA cluster setup
  • A new top navigation bar
  • Operator-based installer changes
  • Plugin and integration changes

And more bug fixes and enhancements.

Support Policy

See Digital.ai Support Policy.

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 upgrade instructions, see:

Digital.ai Deploy 22.3.0 New Features

Here’s what’s new with Digital.ai Deploy 22.3.0.

Install or Upgrade Digital.ai Deploy on Kubernetes

Digital.ai Deploy 22.3 brings you an all new Operator-based installer to install or upgrade Deploy on Kubernetes clusters.

Here’s a list of enhancements.

You no longer need:

  • to download the Operator-based installer zip file.
  • to manually update the cluster resource file—infrastructure.yaml—or the custom resource definition files—daideploy_cr or dairelease_cr. The new installer brings you the installation/upgrade wizard. Installation and upgrade is as simple as running the xl kube install or xl kube upgrade commands and answering the questions in the wizard.
  • a Digital.ai Deploy instance to install or upgrade Deploy or Release
  • to encode the plain text license and repository keystore files to base64 format
  • to generate the Java repository keystore. You can have the Java repository keystore generated at the time of installation or upgrade. YOu can also choose to use the existing keystore, if required.

Supported Cloud Platforms

You can install or upgrade Digital.ai Deploy on the following cloud platforms.

  • Amazon EKS
  • Azure AKS
  • Google Cloud Platform GKE
  • OpenShift (on AWS)
  • Plain k8s (On-premise minikube—only for testing or demonstration purposes. Not for production environments.)

For more information, see Install or Upgrade Digital.ai Deploy on Kubernetes.

Enhancements to XL CLI 22.3.0

The XL CLI has been enhanced as part of the new Operator-based installer. Here’s a list of XL CLI changes.

  • The xl kube command replaces the xl op command.
  • New flags have been added to support the new Operator-based installer.
  • The xl op apply (xl kube apply) command no longer exists. If you use the --dry-run flag to generate the files and apply them later to your cluster, use the xl kube install --ref-install or xl kube upgrade --ref-upgrade commands.
  • The --keep-files flag no longer exists. The YAML files generated during the installation or upgrade are, by default, preserved in the filesystem post install or upgrade for future use.

For more information, see XL CLI Command Reference.

Known Issues

  • D-22765 - In some terminals (Windows), a new line of the same question is added to the command prompt every time you use the arrow key to select one of the options for a multi-line question (with multiple options to select from) of the installation wizard.
  • D-22766 - At the command prompt, users are not able to use the backspace to delete the input when the user input is longer than one line. Users are stuck in the second line of the command prompt.

System Information Tab Enhancements

  • The System Information dialog box is where you must go to understand your Digital.ai Deploy setup.
  • This dialog box presents information categorically in four different tabs—General, Cluster, Installation, and Data Statistics.
  • You must be an Administrator to view the System Information dialog box.
  • The System Information is also part of the Downloadable Support Package.

1664264484428

General tab—provides general Deploy information such as the Deploy version, instance name, server URL, and so on.

Cluster tab—provides Deploy cluster’s information such as the cluster mode, number of cluster nodes, cluster actor system, cluster leader node, active nodes, and so on.

Installation tab—provides the list of installed plugins, deployed hotfixes, and server class paths.

Data Statistics tab—provides statistics on Configuration Items (CIs), Deployments, Control Tasks, Folders, Users, and Placeholders.

For more information, see Digital.ai Deploy System Information.

Changes to the deploy-cluster.yaml and deployit.conf Files—HA Cluster Setup

Digital.ai Deploy 22.3 brings you the following changes related to the high availability (HA) cluster setup:

  • You can no longer set mode to default in the deploy-cluster.yaml file and have Digital.ai Deploy run in HA active-active cluster mode.
  • You must set mode to full in the deploy-cluster.yaml file if you want to run Deploy in HA active-active cluster mode.
  • Setting mode to default means you are running Deploy as a standalone server.
  • Setting mode to hot-standby means you are running Deploy in HA hot-standby cluster mode.

Here’s an example deploy-cluster.yaml configuration file with mode set to full. 

deploy:
  cluster:
    akka:
      actor:
        loggers:
        - akka.event.slf4j.Slf4jLogger
        loglevel: INFO
        provider: akka.cluster.ClusterActorRefProvider
      cluster:
        auto-down-unreachable-after: 15s
        custom-downing:
          down-removal-margin: 10s
          stable-after: 10s
        downing-provider-class: ''
    membership:
      heartbeat: 10 seconds
      jdbc:
        connection-timeout: 30 seconds
        idle-timeout: 10 minutes
        leak-connection-threshold: 15 seconds
        max-life-time: 30 minutes
        max-pool-size: 1
        minimum-idle: 1
        password: '{cipher}gfdqswdksahgdksahgdkas'
        pool-name: ClusterPool
        url: ''
        username: ''
      ttl: 60 seconds
    mode: full
    name: xld-active-cluster
  • The deploy.cluster.akka.remote object has been removed from the deploy-cluster.yaml file.
  • The deploy.cluster.akka.remote.canonical.port key is now configured in the deployit.conf file as deploy.cluster.node.port=25520.
  • The deploy.cluster.akka.remote.canonical.hostname key is now configured in the deployit.conf file as server.hostname.

For more information, see Set up an Active-Active Cluster.

Top Navigation Bar

The Digital.ai Deploy is equipped with a new top navigation bar in line with the unified navigation theme adopted for Digital.ai Release.

1664428016301

Version Upgrades

Supported Databases

Deploy 22.3 supports the following databases.

Database Versions Supported
PostgreSQL 13.6 and 14.2
MySQL 5.7 and 8.0
Oracle 12c and 19c
Microsoft SQL Server 2017 and 2019
DB2 11.1 and 11.5

Plugins and Integrations

Here’s what’s new and changed with plugins and integrations.

Podman Plugin

The Digital.ai Deploy—Podman 22.3.0 plugin—xld-podman-integration—has the following new specs added:

  • podman.PodSpec—this CI creates a Podman pod deployable.
  • podman.ContainerSpec—this CI creates a deployable for a Podman container.
  • podman.NetworkSpec—this CI creates a deployable for a Podman network.
  • podman.SecretSpec—this CI creates a Podman Secret deployable.

Kubernetes Plugin

The Digital.ai Deploy—Kubernetes 22.3.0 plugin—xld-kubernetes-plugin—has the following enhancements:

  • Auto-discovery of Kubernetes master and namespace
  • No support for IngressSpec
  • Fixed an issue with the update_strategy caused in case the deployment IDs are more than 57 characters long.

JBoss Domain Plugin

Fixed an issue with the JBoss Domain plugin that caused the interactive sudo connection to fail.

Azure Plugin

Added the following placeholders—Operating System Type and Runtime Language—to support the creation of Function Apps in Azure from Deploy.

Oracle Web Logic Server (WLS) Plugin

Fixed an issue with the WLS plugin that caused rollback to fail after a successful update of a Weblogic Side-by-side application.

Websphere Application Server (WAS) Plugin

Fixed an issue with the Check Cluster Is Ready Interval setting to prevent incessant attempts to start the cluster (the was.cluster CI).

OpenShift Plugin

Fixed an issue with the undeployment task that runs in a loop even after deleting the OpenShift project.

Bug Fixes and Field Incidents—22.3.7

  • D-22947 - Fixed issue with user privileges that allowed users to modify other user accounts
  • D-23171 - Fixed issue with user privileges that allowed users to view information about other user accounts
  • D-23843 - Fixed System information page load error when using different databases for reporting and repository.
  • D-23971 - Fixed System information page load error with Microsoft SQL Server as database.

Bug Fixes and Field Incidents—22.3.6

  • D-23221 - Fixed the login screen message to avoid overflow in case of long usernames that contain no whitespaces.
  • D-23121 - Fixed issue causing an empty Plugins page to be displayed on the XLD operator server.
  • D-23216 - Fixed issue causing the xl kube check command to fail when keytool is not installed.
  • D-23365 - Fixed issue with validating password complexity criteria during XLD Operator setup.
  • D-23001 - Fixed the ‘Repository Entity not found’ error caused when opening an environment or dictionary associated with directories containing ampersand (&) in their name.
  • D-23336 - Fixed the Master/Work directory cleanup activity to remove all data associated with archived tasks.
  • D-23407 - Added support for IBM-1047 encoding.

Bug Fixes and Field Incidents—22.3.5

This version was skipped and 22.3.6 was released in its place.

Bug Fixes and Field Incidents—22.3.4

  • S-88593 - Fixed CVE-2022-33980 and CVE-2022-42889 vulnerabilities.
  • D-23201 - Fixed the segmentation fault that caused operator installation to fail on Mac OS Ventura.
  • D-23240 - Fixed the incorrect syntax issue that caused the package retention policy to fail when MS SQL Server database is used.
  • D-23372 - Fixed issue with the Digital.ai logo hyperlink on the Deploy page.
  • D-23474 - If you uncomment any properties in the type-defaults.properties file, all backslash () characters will be dropped after server restart. To avoid this, add another backslash as an escape character before all backslash characters.

Bug Fixes and Field Incidents—22.3.3

Note: There is no Deploy version 22.3.2.

  • D-23033 - When you enter the license as clear text in the editor and generate the answers file, the Digital.ai Deploy installation fails. This issue is now fixed.
  • D-23041 - When you enter the operator image input with a colon, the Digital.ai Deploy installation fails. This issue is now fixed.
  • D-21145 - Dictionary version number is out of order in Digital.ai Deploy. This issue is now fixed.
  • D-22125 - Fixed an issue with the Terraform plugin for Digital.ai Deploy that crashes the server.
  • D-22869 - After upgrading Deploy, the non-admin users are unable to view the tasks and reports created by them earlier. This issue is now fixed.

Bug Fixes and Field Incidents—22.3.1

  • D-22411 - Fixed an issue that prevented users from creating new ResourceGroups on Azure clusters.

Bug Fixes and Field Incidents—22.3.0

  • D-22446 - Fixed an issue that prevented users from secondary LDAP servers (on sites with multiple LDAP servers and OIDC enabled) from logging on to Digital.ai Deploy.
  • D-21064 - Fixed a permissions issue that prevented the POST /repository/cis/read API from reading multiple configuration items from the repository.
  • D-21089 - If there are more than 1000 directories that don’t inherit permission from their parent, then non-admin users will not be able to view any CIs. This issue is now fixed.
  • D-21472 - Fixed the duplication of records issue in reports dashboard and deployment task page for non-admin users. This occurs with Oracle database.
  • D-21691 - Fixed an issue that prevented the Digital.ai Deploy users from being logged out automatically at the expiry of the set idle time.
  • D-22038 - If you resume a task after restarting Digital.ai Deploy, the task fails by getting stuck in the Stage artifacts step. It occurs when staging is enabled, and this issue is now fixed.
  • D-22223 - Custom release conditions are not working as expected even though users have proper permission in LDAP and OIDC. This issue is now fixed.
  • D-22298 - A deployment task with a failed step is not resuming because the server is down. However, it does not resume even after the server is operational. This issue occurs with parallel deployments and is fixed now.
  • D-22344 - Upgraded ssh library to support latest ssh ciphers.
  • D-22385 - Fixed the principal name case-sensitive issue that occurs while fetching permissions.
  • D-22547 - Importing a deployment package file with dependent application results in Null Point Exception error. This issue is now fixed.
  • D-20322 - If you use any regex pattern-based property such as file.File.textFileNamesRegex, Deploy escapes the backslash character \ so that it is not lost in server restarts. Should you modify these properties with any other custom values, you must make sure to escape the \ character with another backslash. For example, file.File.textFileNamesRegex=.+\.(cfg | conf | config | ini | properties | props | txt | xml) must have two backslashes as shown in the following example: file.File.textFileNamesRegex=.+\\.(cfg | conf | config | ini | properties | props | txt | xml).
  • D-21747 - When you update the active-user-sessions-enabled property to false in centralConfiguration/deploy-server.yaml file and start the server, the server is not starting and throws an error. This issue is now fixed and active sessions gets disabled in User management.