Release Manual 10.2.x

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 10.2.1

Digital.ai Deploy 10.2.1 has a support term of 12 months from the date of release. For more information, see Digital.ai Support Policy.

New features

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

  • A well-rounded Central Configuration Management feature
  • An option to Force Redeploy applications without having to do delta analysis or cleanup
  • An enhanced Plugin Manager and Plugin Manager CLI to install, upgrade, and delete plugins with ease
  • An enhanced user experience via Unified Navigation menus and widgets
  • A new globalContext object to set attributes with global scope so that you can access them from any of the Deploy’s planning contexts such as pre-plan, deployed, plan and post-plan

  • Enhanced plugins:

    • Kubernetes
    • Apache Tomcat
  • New plugins for:

    • Azure Cloud Service
    • Cloud Foundry CLI
  • New APIs

Central Configuration Management

The Central Configuration Management feature—part delivered in Deploy 10.1—has been enhanced in Deploy 10.2.1.

The following noteworthy enhancements and changes are part of the Central Configuration Management feature in Deploy 10.2.1:

  • Added a new centralConfiguration/deploy-artifact-resolver.yaml file
  • Moved the Akka DNS override configuration properties from conf/xl-deploy.conf to centralConfiguration/deploy-server.yaml
  • Moved Deploy database configuration properties (both repository and reporting database configuration properties) from conf/xl-deploy.conf to centralConfiguration/deploy-repository.yaml and centralConfiguration/deploy-reporting.yaml files respectively.
  • Moved Deploy server configuration properties from conf/xl-deploy.conf to centralConfiguration/deploy-server.yaml
  • Moved the task configuration properties from conf/xl-deploy.conf to centralConfiguration/deploy-task.yaml
  • Moved the satellite configuration properties from conf/xl-deploy.conf to centralConfiguration/deploy-satellite.yaml
  • Renamed the deployit-defaults.properties file as type-defaults.properties
  • Moved some of the configuration properties from the deployit.conf file to deploy-client.yaml and deploy-server.yaml files—one for configuring the client and the other for the server.
  • The deploy-client-gui.yaml file is no longer available and all its configuration properties have been subsumed by the deploy-client.yaml file
  • AES algorithm for encryption/decryption of sensitive configuration data such as passwords
  • Multiple keys and key rotation for added security

The above list of changes is just for your understanding. The configuration files and properties are auto-migrated when you upgrade to or install Deploy 10.2.1 (or later). No user intervention whatsoever is needed when you upgrade to or install Deploy 10.2.1.

For more information, see Central Configuration Management

Force Redeploy applications

At times you may want to just redeploy an already deployed application by merging and overriding the content without doing the delta analysis or cleanup. Such situations arise when you want to simply destroy/uninstall the existing deployed (application) and install the application again.

Select the Force Redeploy property (check box) of the deployed application from the Deployment Properties dialog box and do the deployment in such situations.

force-redeploy

Though this feature works with all the plugins, here’s a list of plugins that were tested and qualified in Deploy 10.2.1. Other plugins would be included in the test coverage in due course.

  • File plugin
  • Command Plugin
  • Database plugin
  • Kubernetes plugin
  • AWS plugin
  • Terraform plugin
  • Webserver plugin
  • The Force Redeploy feature is not supported for plugins that are used to deploy WAR type deployables—Tomcat and JEE plugins, for example.
  • The deployment rollback feature is broken after you Force Redeploy an application. This would be fixed in one of the upcoming releases.

Plugin Manager and Plugin Manager CLI

Digital.ai Deploy 10.2.1 is equipped with an enhanced Plugin Manager and a new Plugin Manager CLI.

The enhanced Plugin Manager:

  • Lets you search and install plugins (Browse tab)
  • Shows an Upgrade button for plugins that are installed already and lets you upgrade the plugins whenever a new version is available (Browse tab)

    deploy-plugin-manager

  • Lets you upload a new plugin or a new version of an already installed plugin (Installed tab’s Upload new plugin file)

For more information, see Plugin Manager

Deploy 10.2.1 is equipped with a new Plugin Manager CLI utility to delete plugins from both the filesystem and database. For more information, see Plugin Manager CLI

Term-based package retention policy

In addition to the count-based package retention policy, you can now define and rollout package retention policies based on a fixed term (in days). In other words, you can enforce a package retention policy that lets you purge packages that are older than a certain number of days. For more information, see Package retention policy documentation.

Unified Navigation—UX enhancements

One of the objectives of Deploy 10.2.1 is to provide better user experience. Digital.ai Deploy’s navigation menus, icons, and widgets have been totally revamped to enhance the usability. For more information, see Get started with the Deploy user interface

unified-navigation

New globalContext object for use in all planning contexts

You can now use the globalContext object to set attributes globally and get those attributes in different planning contexts (such as pre-plan, deployed, plan, and post-plan) while executing Jython/Python scripts. For more information, see The DeploymentPlanningContext

Digital.ai Deploy Azure cloud service plugin

  • Deployment of cloud service spec to the Azure cloud through the Digital.ai Deploy
  • Digital.ai Deploy Azure cloud service plugin support is now extended to:

    • Create a virtual network
    • Create a storage account
    • Create a public IP address

Digital.ai Deploy Cloud Foundry CLI plugin

Implemented multiple application deployment using single manifest file in the Cloud Foundry CLI integration plugin. For more information, see Cloud Foundry CLI plugin

Digital.ai Deploy Kubernetes plugin

The Kubernetes plugin is enhanced as follows:

  • The value property provides details about the deployment endpoints
  • The secrets are deployed on Kubernetes cluster with the CI name instead of the file name

Digital.ai Deploy Apache Tomcat plugin

The default connection pooling library of Apache Tomcat plugin is updated to Apache Commons DBCP 2.x from DBCP 1.x.

API changes

  • Added a new new API to get the overall number of deployments per deployment state—GET /report/status-overview. For more information, see GET /report/status-overview API documentation.
  • Added a new new API to get the number of deployments per application and environment—GET /report/app-env-status. For more information, see GET /report/app-env-status API documentation.
  • Added a new new API to get a summary of the tasks currently running and waiting in the queue—GET /queue/summary. For more information, see GET /queue/summary API documentation.
  • Added a new new API to list all the QueuedTasks waiting in the task queue—GET /queue/tasks. For more information, see GET /queue/tasks API documentation.

Bug fixes—10.2.1

  • [ENG-2488] - The incorrect server-side error message that was used in place of the form-level validation error (if you leave the mandatory Name field empty when you create a configuration item) has been fixed.
  • [ENG-2618] - Fixed an issue that prevented users from creating deployment packages that consist of a single file with no content (0 bytes) on Deploy sites that use the Oracle database.
  • [ENG-4509] - Fixed a security vulnerability to prevent directory traversal attacks.
  • [ENG-5621] - The maximum number of characters allowed for Deploy placeholders is 255 characters.

Digital.ai Deploy 10.2.2

Kubernetes Operator-based Installation

Note: Helm Charts-based installer is no longer available for Digital.ai Deploy 10.2 and later.

  • Digital.ai Deploy 10.2.2 brings you a simple and sophisticated Kubernetes Operator-based installer to install Digital.ai Deploy on Amazon EKS, Azure AKS, and OpenShift on AWS clusters
  • You can download the new Kubernetes Operator-based installer from the Deploy/Release Software Distribution site
  • Once you download the installer Zip file, Digital.ai Deploy installation is as simple as adding a few configuration parameters and custom resource definitions to the installer files and running the installer

For more information about Kubernetes Operator-based installation, see Kubernetes Operator.

Bug fixes—10.2.2

  • [ENG-6632] - Plugin Manager CLI Improvements

Known issues

  • [ENG-6866]—Users without Admin privileges are not able to view scheduled deployment/control tasks as soon as you turn the Deploy Maintenance Mode on.

Digital.ai Deploy 10.2.3

Kubernetes Operator-based Installation

With Deploy 10.2.3, the Kubernetes Operator offers the following enhancements:

Bug fixes

  • [ENG-6600] - Fixed the issue where the Terraform plugin does not function when Stitch is enabled.
  • [ENG-6934] - Rollback is not functional when “Force redeploy” Deployment property is enabled. Instead undeploy / delete manually based on the requirement.
  • [FI-496] - Fixed Deploy 9.7.10 and 10.0.0 performance issues.
  • [FI-659] - Fixed the issue with large DARs that caused the Deploy application to go down.
  • [FI-753] - Fixed the Digital.ai Deploy Connection Lost Error.

Known issues

  • [ENG-6622]— MissingDirectoryReferenceException message is displayed when you upgrade from Deploy 10.1 to Deploy 10.2.
  • [ENG-7005]—Currently there is an issue when you upgrade from Deploy 9.8.1 to Deploy 10.2.1 with Oracle 19c. You can get a hotfix for the issue from the support team. The fix is will be included with the 10.2.3 release.