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
anddeployit.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
ordairelease_cr
. The new installer brings you the installation/upgrade wizard. Installation and upgrade is as simple as running thexl kube install
orxl 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 thexl 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 thexl kube install --ref-install
orxl 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.
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
todefault
in thedeploy-cluster.yaml
file and have Digital.ai Deploy run in HA active-active cluster mode. - You must set
mode
tofull
in thedeploy-cluster.yaml
file if you want to run Deploy in HA active-active cluster mode. - Setting
mode
todefault
means you are running Deploy as a standalone server. - Setting
mode
tohot-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 thedeploy-cluster.yaml
file. - The
deploy.cluster.akka.remote.canonical.port
key is now configured in thedeployit.conf
file asdeploy.cluster.node.port=25520
. - The
deploy.cluster.akka.remote.canonical.hostname
key is now configured in thedeployit.conf
file asserver.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.
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.17
- D-26046 - Fixed an issue where the application could not be deleted as rollback failed to update Infra-CI with the correct version.
Bug Fixes and Field Incidents—22.3.16
- D-27083 - Fixed an issue with the import functionality that was blocking the import of a DAR (DAR file of an application), which included a reference to another CI.
- D-27237 - Fixed an issue where upgrading Deploy from version 9.7.4 to 22.3.6 resulted in an error when attempting to import a new DAR file for an application.
- D-27061 - Fixed an issue with the
help
command inxl kube upgrade --help
to display the correct upgrade instructions.
Bug Fixes and Field Incidents—22.3.14
- D-26151 - Fixed an issue with
xld-deployment-package-status
queue consumer, which was growing infinitely with no signs that Deploy is processing the items.
Bug Fixes and Field Incidents—22.3.13
- S-93742 - Fixed CVE-2021-35515 vulnerability.
- S-93816 - Fixed CVE-2022-45868 vulnerability.
- D-24625 - Fixed an issue with starting Deploy after upgrading from version 22.2.x to 22.3.x.
- D-25271 - Fixed an issue with the HashiCorp Vault plugin that did not allow you to save multiple lookup values in the "Authentication AppRole" section.
- D-25760 - Modified the
xld_ci_properties
table id column type from integer to bigint to accommodate large number of records. - D-25558 - Fixed an issue with deploying provisioning packages when CI names contain contextual placeholders.
- S-93426 - Fixed the host header injection JavaScript vulnerability in Digital.ai Deploy.
- D-23577 - Fixed archive mappings in the
deploy-artifact-resolver.yaml
file that caused issues with placeholder replacement.
Bug Fixes and Field Incidents—22.3.12
This version was skipped and 22.3.13 was released in its place.
Bug Fixes and Field Incidents—22.3.11
- D-25096 - Fixed an issue with the Deployment screen that caused multiple errors upon clicking the
Finish
button. - S-93329 - Fixed CVE-2023-20883 vulnerability.
- S-92929 - Fixed an issue with Abort and Stop operations not working on hung tasks.
Bug Fixes and Field Incidents—22.3.10
- D-23332 - Fixed the issue with saving two lookup values—role ID and secret ID—in
secrets.hashicorp.vault.Server
. - D-23763 - Fixed the issue with non-admin users being unable to see deployments in reports.
- D-23851 - Fixed the issue with some reports missing from Reports > Deployments panel after upgrade.
- D-24093 - Fixed the
maximum number of expressions in a list is 1000
error when non-admin users try to view placeholders and there are more than 1000 directories that don't inherit permission from their parent. - D-24130 - Fixed the
incoming request has too many parameters
error when non-admin users tried to access Deploy reports. - D-25223 - Fixed an issue that caused deployments to fail when customers used credentials stored in
overthere.SshJumpStation
instead of the username and password combination.
Bug Fixes and Field Incidents—22.3.9
- D-23711 - Fixed issue with folder permissions that caused existing permissions to be removed when new permissions are added using the 'Select All' option.
- D-23962 - Fixed the permissions error encountered by non-admin users when searching for Dictionary values using the search by placeholder option in Explorer.
- D-23172 - Added a fix to expire all active user sessions when a user resets their password.
Bug Fixes and Field Incidents—22.3.8
- D-24065 - Fixed the
CheckConnection
issue with the Deploy Task Engine when setting up a multi-node cluster with OIDC. - D-24174 - Fixed the
CannotLocateArtifactException
issue while deploying Maven artifacts. - D-23170 - Fixed an issue with the
GET /api/v1/roles
API to prevent unauthenticated users from viewing role names and IDs of other users. - S-89672 - Optimized the support .zip output to include information based on
supportpackagasettings
configuration indeploy-server.yaml
.
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 incentralConfiguration/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.