Digital.ai Deploy 22.0.0

Digital.ai Deploy 22.0.0 includes the following new features:

• Separate server distribution to install the Deploy worker
• Kubernetes Operator enhancements
• Deploy usage metrics (Telemetric Data) for diagnosis
• Plugin Manager enhancements
  • File-based installation of custom plugins
• Updates to the following Deploy plugins
  • Helm plugin
  • Kubernetes plugin
  • Docker plugin
  • IIS plugin
  • WAS plugin
  • WLS plugin
• New Versioning Scheme for Digital.ai Deploy

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 detailed instructions based on your upgrade scenario, refer to Upgrade Deploy.

Digital.ai Deploy 22.0.0 New Features

Here's what is new with Digital.ai Deploy 22.0.0.

Separate Server Distribution to Install the Deploy Worker

With Deploy 22.0, you can install the worker on a separate server—using the new Deploy Task Engine installer. The new Deploy Task Engine installer is an abridged version of the Deploy installer that has the bare essentials required to install and run Deploy Workers on a separate server. This means that the Deploy Task Engine has just the code related to execution of tasks, which reduces the load on the server. For more information, see Install Deploy Worker Using Task Engine.

Kubernetes Operator Enhancements

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

• Kubernetes Operator supports installation of Digital.ai Deploy on Google Cloud Platform (GCP)
• You can migrate to Deploy 22.0 from Deploy 10.2 on the following platforms:
  • Amazon EKS
  • Azure Kubernetes Service (AKS)
  • Kubernetes On-premise
  • OpenShift cluster on Amazon EKS
  • OpenShift cluster on VMWare vSphere
  • Google Cloud Platform (GCP)

For more information, see Operator Based Installation.

Deploy Usage Metrics (Telemetric Data) for Diagnosis

Deploy Administrators can now download key Deploy usage metrics data for troubleshooting and diagnosis.

Click Usage Metrics from the Help menu to download the telemetric data as a Zip file.

This zip file includes the following data (in JSON format).

• ConfigurationItemsCount
• DeploymentsCount
• ListConfigurationItems
• ListDeployments
• PluginsCountByCI
• PluginsCountByDeployment
• SubFoldersCountByCI
• UsersCountByCI

Plugin Manager Enhancements

Plugin Manager is considerably enhanced to ensure it works smoothly on all environments.

• For CI/CD scenarios of custom plugin development, the Plugin Manager supports installation of custom plugins directly into the plugins/__local__ folder, mimicking the pre-10.2 behavior. For more information, see the File-based Installation of Custom Plugins.
• Added install-or-update endpoint, to make it more explicit if Deploy should detect and remove a previous version of the plugin.
• Plugin Manager detects version upgrades of custom plugins, based on semver semantics. In most cases, it is no longer needed to remove the previous version of the plugin.
• List of official plugins is automatically refreshed once a day.
• Fixed performance issues on Windows.
• Plugin Manager warns if a plugin contains a type that is already defined by another plugin.

File-based Installation of Custom Plugins

IMPORTANT: From Deploy 10.2, the plugins are stored in the database and are no longer maintained in the plugins folder. This has some implications on product upgrade, and installation and upgrade of plugins.

• You can now install custom plugins by copying them to the plugins/__local__ folder. However, you must specify a start-up flag to trigger this functionality.
• To run the bin/run.sh command directly, you must add the -plugin-source=filesystem flag.
• When using the Docker container, you must set environment variable—PLUGIN_SOURCE=filesystem.

Note: When running multiple nodes in a cluster, you only need to install the custom plugin on one node. Additional nodes will pick up the new plugin from the database when you restart the server.

Here is a summary of the behavior for plugin installation:

Version	Official Plugins	Custom Plugins
Deploy 10.1 and earlier	Bundled in plugins/xld-official Installed through UI (single-node setups only)	File copy to plugins/__local__
Deploy 10.2	Bundled in plugins/xld-official Installed through UI (supports multi-node setups)	Upload through UI
Deploy 10.3	Bundled in plugins/xld-official Installed through UI (supports multi-node setups)	Upload through UI REST API
22.0 and later	Bundled in plugins/xld-official Installed through UI (supports multi-node setups)	Upload through UI REST API File copy to plugins__local__ (with startup flag) plugin-manager-cli

Note: The -plugin-source start-up flag is ignored on first start up post installation or upgrade.

For more information, see Manage Plugins.

Plugins and Integrations

• Google Cloud Kubernetes Plugin

  • The x509 certificate-based authentication has been deprecated in GKE. Deploy 22.0 brings you the new token-based authentication for Google Cloud Kubernetes (GKE). You can now use token-based authentication with Google Cloud Kubernetes (GKE).
  • You can now use Amazon EKS and Azure AKS service accounts when you want to log on to (access resources) Amazon EKS and Azure AKS Kubernetes clusters using Deploy's Kubernetes plugin.

• Helm Plugin

  Fixed an issue that caused incorrect exceptions (warnings) during helm chart deployment and un-deployment using the UseClusterConfiguration feature.

• Docker Plugin

  Fixed the No basic auth error that occured when you pull Docker images.

• IIS Plugin

  Fixed—Destroy Application task was taking longer than usual to complete.

• WAS Plugin

  Resources with identical names are now supported.

• WLS Plugin

  Fixed—EAR deployment order not happening per the SIDE by SIDE setting.

New Versioning Scheme for Digital.ai Deploy

The previous major version is Digital.ai Deploy 10.3.x. For this version we made the jump to 22.0. We have done that to harmonize version strategies across the various products in the Digital.ai portfolio.

Going forward, the Digital.ai Deploy's versioning scheme follows the YY.a.b format, where a is the major release version number and b is the maintenance release version number. The versioning scheme is not very different than it was before.

• The first number (YY) refers to the last two digits of the year the version was released on. For example, in year 2022, all versions start with 22.
• We will release a major version every quarter, starting with '0'. So the first version of the year is 22.0 and the last will be 22.3. The version after that will be 23.0, to be released in the first quarter of 2023.
• The final number is the maintenance version. As a rule, maintenance versions will not contain new features and will be backwards compatible with other maintenance versions of the same major version. That means that you can roll back 22.0.1 to 22.0.0, for example. Database migrations and other incompatibilities might occur when going from one major version to another. So you can't rollback from 22.1.0 to 22.0.9, for example.

Bug Fixes

Bug Fixes and Field Incidents—22.0.0

• ENG-7800—Fixed an issue that caused file (archive) deployments tasks to run endlessly post-upgrade to 10.3 or later.
• ENG-7980—Fixed the broken Jython patch for issues 2618 and 2894.
• ENG-8336—Fixed a plugin synchronization issue on windows that prevented the old plugin from being deleted when a new plugin with the same name was uploaded.
• ENG-8812—Digital.ai Deploy and Release are not susceptible to log4j vulnerability. Though Digital.ai Deploy and Release were bundled with log4j-to-slf4j and log4j-api files, these JAR files cannot be exploited. While neither these files nor Digital.ai Deploy and Release are susceptible to attack due to this log4j vulnerability, some threat detection systems may flag these files. To avoid any such false positive threat indications in future, the latest log4j library files (interface and supporting third party libraries) were bundled with both Digital.ai Release and Deploy. For more information, see this article.
• FI-847—Fixed the issue where invalid archive is not copied when Replace Placeholders is enabled.
• FI-853—Fixed the latency issue that caused some delay in loading the Deploy application logo.
• FI-856—Fixed the issue where the non-admin users cannot view the old archived tasks that were visible before the upgrade.
• FI-868—Fixed the OIDC session time out upon inactivity issue. Fixed the issue with user session timeout handling where user had to re-login despite OIDC session being active. Deploy will now use the already active OIDC session without forcing user to re-login.
• FI-869—Fixed the issue with importing file.Folder CI that has accented characters.
• FI-872—Fixed the XL CLI user list fetching issue.
• FI-880—Fixed the issue with scheduled tasks where user with proper permissions is not able to see them.
• FI-884—As part of making lock plugin more resource friendly, a new option - lockRetryAsync is introduced. When set to true (the default value), the retry releases the currently executing thread to the pool instead of blocking it. This will improve the overall system responsiveness. When explicitly set to false, the lock plugin blocks the currently executing thread.
• FI-896—Fixed the issue with cluster AutoDowning where XLD fails to start in hot-standby mode.
• FI-897—Updated warnings for unresolved placeholders when updating the deployment.
• FI-900—Fixed the issue with http.context.root configuration when accessing Reports.
• FI-910—Fixed the issue where the accented characters were not displayed in Dictionary upon saving.
• FI-934—Fixed the crowd integration issue in Deploy 10.3.3.
• FI-936—Fixed the issue that limited maximum number of expressions in a list to1000.
• FI-938—Fixed the deployment issue that occurred when Deploy is started as a service.
• FI-951—Fixed the issue where the users/roles having all the permissions on subfolders are unable to import the Application permission.
• FI-955—Fixed the Task archive issue with mysql database.

Bug Fixes and Field Incidents—22.0.1

• FI-954—Fixed a UI issue that prevented automatic user session timeouts past the threshold idle time.

Bug Fixes and Field Incidents—22.0.2

• ENG-9080 — Fixed an issue where the cluster data was not properly persisted in the database.
• FI-953 — Fixed an issue that created a deployment task and indefinitely queued it when wrong hostname was entered for the wls.Domain type.
• FI-982 — Fixed an issue that displayed an error in the Register Deployed section even after deployment was cancelled.
• FI-1006 — Fixed an issue that prevented the display of a particular activity in the monitoring and report pages.
• FI-1011 — Fixed an issue that prevented the Run.sh command from starting the satellite with wrapper Java options.
• FI-1022 — Fixed an issue that caused constant execution of PermissionServiceAttachUpgrade task upon server restart.

Bug Fixes and Field Incidents—22.0.4

• D-20598 - Fixed the INTERACTIVE_SUDO connection type vulnerability.
• ENG-9087 - Fixed an issue with install-service.sh and install-service.bat by updating them to include the plugin-source=database flag.
• FI-930 - Fixed an issue with the resolved placeholders that were not getting displayed in the Environment view when the application is deployed.
• ENG-7906 - Fixed an issue due to which only users with Report-View permission were able to download the generated report.
• ENG-5298 - Fixed an issue with the resolved placeholders that were not storing the values while deploying the iis.WebContent to the overthere.SmbHost.

Bug Fixes and Field Incidents—22.0.5

• D-18895 - Fixed an issue with the user session expiry for a deleted user, who has the permission or access to an active session. Now, a deleted user will be denied access to an active session.
• D-20452 - Fixed an issue with Deploy that is set up in HA mode, which shows a Null pointer exception while making changes in Instance customization.
• D-20538 - Fixed the deadlock issue within the Lock plugin.
• D-20857 - Fixed an issue with the permissions service REST API results, which were returning all configuration items instead of the folders.

Bug Fixes and Field Incidents—22.0.6

• D-18337 - Fixed a UI issue with the Resolved Placeholders table to show the lengthy Dictionary entries (with ellipses) fully when hovered over.
• D-19883 - Fixed an issue that removed the Digital.ai logo up on adding a custom logo.
• D-20191 - Fixed the Bad Request error (when roles were created) that occurred on sites with standalone Deploy permission service.
• D-21367 - Fixed a UI issue that prevented long Dictionary title from being shown in the Dictionaries section of the Environment view.
• D-21443 - Fixed an issue that caused deployments with long Dictionary title to error out.

Bug Fixes and Field Incidents—22.0.7

• 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-21099 - Fixed a configuration issue in the export folder of Deploy.