ADCM releases

Added the new Widget view mode to the Clusters page. In this mode, clusters are displayed as widgets with extended information

Redesigned the Overview tab on the cluster page. Added more detailed information about the cluster status

Added support for Celery Worker as an alternative job execution environment. Celery Worker installation is available via ADCM Installer version 1.2.0. This feature is experimental and is not recommended for production environments

On the Bundles and Cluster pages, added a warning if the product version in use is outdated and will prevent future ADCM upgrades. Before upgrading ADCM, the product must be updated to the latest version

Added support for Ansible 2.21

On the Hosts page, implemented the ability to perform actions and operations on multiple hosts simultaneously. When using the minimum recommended ADCM host specifications, it is not recommended to run an action on more than 30 hosts simultaneously

Added support for Consul. If the corresponding environment variables are configured when starting the ADCM container, ADCM and Celery Worker register their instances in Consul

Added the new built-in service_manage function, which allows managing the list of cluster services

Changed the container launch mechanism. If the required initialization steps are not completed, the container will not start. All launch information is displayed in the Docker container logs

Changed the approach to generating inventory files. Identical host parameters are now grouped together, which significantly reduces the size of the inventory file and speeds up action execution

In the cluster update modal window, added the ability to view information about the changes that will occur during the update. Each product independently specifies this information using the description attribute

Adapted ADCM internal actions to work with Ansible 2.21

All processes inside the Docker container run as a non-privileged user with a fixed UID/GID 10001:10001 instead of root. Before upgrading to version 3.0.0, the ownership of the /adcm/data directory must be changed according to the Upgrade article

The execution of built-in functions is now logged to the ansible-stdout.txt and ansible-stderr.txt files of the corresponding jobs

The object configuration interface has been reworked. Most parameters can now be edited without opening a modal window

Simplified the cluster update interface by removing unnecessary steps

Modified the action launch modal window: the last two steps were combined to simplify the launch process

Updated the error message shown when saving a configuration. Field names used in the web interface are now displayed instead of internal service names

Added a button to quickly copy the host name to the clipboard on the Hosts page and the Hosts tab of the cluster page

Reorganized the Ansible plugins directory structure to support FQCN naming in playbooks

ADCM 3.0.0 is mandatory for installation and cannot be skipped during an upgrade

Fixed a bug that caused the Wizard to unexpectedly stop when changing the cluster topology

Fixed an issue where returning to a previous Wizard step required re-filling required fields

Eliminated a data race when obtaining tokens in Status Server thanks to the community contribution

Fixed a vulnerability that allowed unsigned bundles to modify the contents of other files in the container

Updated Python for ADCM to version 3.12

Restricted access for the status user, which is used to send object states from hosts to Status Server

Updated key ADCM components to the latest versions, eliminating known vulnerabilities

Removed support for Ansible 2.8 and 2.9

Removed support for the contract versions 1.0 and 2.0

Empty content of secretfile configuration parameters is no longer encrypted

Added integration with Vault for centralized secret storage. To use Vault with existing ADCM installations, it is required to perform secrets migration

Added the ability to edit descriptions of configuration groups and action host groups for clusters, services, components, and hostproviders

Added support for the scripts_template property for more flexible cluster upgrades. This property allows dynamic generation of subjob sequences

Added the ability to skip optional steps in Wizard to reduce action execution time. For steps with scripts_template, the optional required attribute can be specified

Extended the capabilities of the adcm_check plugin: added support for the optional severity attribute to define check criticality. Possible values: error, warning, info

Added support for using Wizard with action host groups

Added information about existing cluster imports to the before_upgrade section of the inventory file before cluster upgrade

Introduced a restriction to prevent issues during cluster upgrade: upgrade is not allowed if at least one host is in maintenance mode

Fixed an issue with applying activatable groups within nested groups

Fixed an issue with a concern remaining for a cluster after executing the adcm_config plugin

Improved audit logs for authorization operations: login attempts with incorrect passwords are now explicitly recorded

Fixed an issue with disabling maintenance mode for a service if it was enabled on a host. Now information about the reasons for service maintenance mode is displayed correctly

Improved search functionality on the audit page: added the ability to filter by logins used during authentication attempts

Performed code refactoring: all SQLite-related code was completely removed

Consolidated existing database migrations into a single migration to speed up ADCM startup

Fixed issues related to the interface behavior on the configuration page when selection_group is present

Added cluster relevance check during ADCM upgrade. Installing a new ADCM version is blocked if clusters use contract_version that is no longer technically supported

Implemented the new before_upgrade_clean function that clears the before_upgrade section in the inventory file. Reducing the inventory file size speeds up job execution

Unified email validation rules for user creation. Frontend and backend now apply the same checks, which eliminates discrepancies between the web interface and the server

Fixed the issue where text search in logs on the subjob page worked only on text visible on screen

Fixed the issue with product filtering on the Clusters page

Implemented the contract version 2.1 (contract_version: "2.1") which removes support for Ansible 2.9

Fixed the issue that occurred when upgrading ADCM to the version 2.7.0 and later. Updated migration script that previously ended with an error when configuration groups were present. Users who experienced issues when upgrading to 2.7.0 and later are recommended to upgrade to 2.10.1

On the configuration version tab, added the login of the user who made object configuration changes to simplify auditing

Added a navigation mini-map to the object configuration page to improve usability when working with configurations containing many parameters

Added the ability to collapse the left navigation menu to improve usability on screens with limited resolution

Added a notification to inform users when an object configuration is edited by another user

Added the contract_version property to the config.yaml file to check compatibility between ADCM and product versions

Added the message on the object configuration page if the object has no configuration

Updated the text of the notification that appears when attempting to enable maintenance mode if it is not supported by the current product version

Fixed the issue with filtering objects of a removed cluster on the Jobs page

Fixed the issue with updating the status of jobs that did not complete correctly when the ADCM container was restarted

Implemented removal of the object config group when the object no longer has a configuration after a product upgrade

User session is now terminated when the browser is closed to enhance security

Fixed a bug that caused the ADCM failure when using an unencrypted password

Fixed a bug that caused default values for new password input fields to be stored in plain text when updating the product

Fixed the error that occurred when creating a subhost if the host configuration contained nested groups

Fixed the error that occurred during the product update when configuration parameters of the file type were used

It is now possible to leave comments when running actions. These comments are displayed on the Jobs page

Added the ability to run ADCM with HashiCorp Consul environment variables intended for products. These variables will allow products to integrate their services with HashiCorp Consul

Added support for nested groups. To improve navigation, configurations can have multiple levels of nested groups

Added support for mutually exclusive groups. To improve navigation, a new configuration element was added that allows you to select one group from a list

UUID of each object was added to the config.json configuration file

Name of an object for which an action was started was added to the drop-down list of jobs that appears when you click the job indicator (the bell icon)

Eliminated ambiguity when using filters on the Bundles page

Added the ability to go to API description from the drop-down list in the upper right corner of the web interface pages

Added the ability to view job execution logs in the full-screen mode

Detailed information on available versions was added to the cluster update dialog box

Added the icon for quick access to parameter descriptions when working with object configurations. Hovering over the icon displays an expanded description of the selected configuration parameter

Fixed a problem with the frozen screen containing logs of a long-running job

Fixed display of a service information

Fixed the error that occurred when mapping services to hosts and caused changes in the component order

Clicking All hosts led to the selection of all hosts including those that were in maintenance mode

Fixed a bug that caused an empty tooltip to be displayed when selecting mandatory configuration parameters

Upgraded the urllib3 library to 2.5.0

Upgraded the requests library to 2.32.5

Upgraded the social-auth-app-django library to 5.5.1

Removed the pip library

Upgraded the Django library to 5.2.7

Removed the sqlite-libs library

Upgraded the setuptools library to 80.9.0

Removed the pycryptodome library

Upgraded the cryptography library to 45.0.7

Added support for Ansible 2.16

Implemented the new config_apply function in the prototype script parameter

Added the ability to reuse a host in different clusters

The configuration page was redesigned

Cluster actions with the host_action: true parameter were added to the list of host actions on the Hosts tab of the cluster page

Fixed the error with incorrect information in logs on the Ansible [stdout] tab

Fixed the error that occurred when trying to download logs of an action host group

Fixed the error that occurred when comparing configuration changes made using the adcm_config module

Fixed a bug that caused the modal window with an action to close when the previous action was completed

Fonts used in ADCM are stored locally and not downloaded from the Internet

Deprecated API v1 was removed from ADCM

The Yandex Cloud hostprovider bundle version 3.9 and below is no longer supported

Fixed the error that occurred if a bundle contained a job after removing a service by the adcm_delete_service module

Improved flag management

Added the ability to create a configuration revision

Updated the API v2 schema to bring it to a consistent state

Fixed the error with the status code 500 for an action containing the config_jinja parameter with an empty default value

Fixed the adcm_min_version parameter check when uploading a bundle

Fixed a bug that occurred when uploading a bundle with an empty configuration

Fixed the display of the Sync interval configuration parameter that could contain a negative value

In the bundle_revert function, added the ability to recover deleted objects

Refactored the bundle upload mechanism

Extended the hc_apply functionality

SQLite is no longer supported

Introduced restriction for unsigned bundle uploads

Introduced the unsafe option for Ansible inventory parameters of the string type

Added the groups variable to the Jinja2 template rendering context

Corrected UI scaling issues on high-resolution monitors

Eliminated host variable duplication in inventory

Disabled legacy TLS versions in the nginx configuration

Corrected display of the empty service configuration

Fixed incorrect schema path resolving during upgrade

Resolved the action host group termination error

Fixed the cluster blocking issue when running an action on the hostprovider

Fixed the service blocking issue when the host is blocked

Fixed the issue of pagination number reset when selecting a previously saved configuration

Prevented display of unnecessary outdated configuration flags

Fixed the cluster statuschecker accuracy after the upgrade

Corrected visibility of the ADCM Ansible settings

Optimized the ADCM image build process

SQLite support will be discontinued from ADCM 2.7.0

API v1 will be deprecated and removed from ADCM in the third quarter of 2025

Fixed the issue of calculations for collecting statistics when sending statistics is disabled

Fixed the issue with updating already installed old versions of ADCM

Added ability to launch actions in non-blocking mode which allows running actions in parallel or executing long actions without fully blocking objects

Redesigned the job page

Upgraded Django to 5.1.1 requiring PostgreSQL 13 or later

Fixed the template loader issue for the Jinja environment

Fixed a hostprovider archive naming to include the hostprovider details in downloaded logs

Fixed a service deletion error occurred when removal was wrongly blocked by remaining tasks in the CREATED status

Backported the hashi_vault plugin for Ansible 2.9

Corrected the WebSocket event name from create_provider_concern to create_hostprovider_concern

Added host sorting by state in the UI

Extended logging settings to set log levels for each log type

Optimized the audit code; improved performance and maintainability

Enhanced the APIv2 logic for creation, deletion, and distribution of concerns

Refactored dump-restore to support the secretfile type and the maintenance mode

Implemented consistent host sorting on the host-component mapping page

Fixed the configuration parameter type file/secretfile in the action config to pass content instead of paths

Enabled min/max constraints for integers in config_jinja to resolve server errors with the status code 500

Fixed the issue with missing operations in the audit.log files in CEF format

Fixed the service dependency errors after adding components

Resolved issues with activatable groups in scripts_jinja

Fixed the multiple bundle upload issue

Fixed the incomplete Ansible log output in the UI

Fixed auto-reloading the service configuration page

Eliminated the possibility of multiple uploads of the same bundle in parallel sessions

Eliminated the possibility of saving the host-component maps with components on hosts in the maintenance mode

Extended statistic collection

Removed the deprecated logrotate functionality

Starting with ADCM 2.5.0, the minimum required version of PostgreSQL will be 14

Introduced action host groups, which are designed to launch actions on several hosts added to a group

Updated the behavior of the outdated_config flag for objects with the created status

Flags are now correctly removed from hosts when a cluster is deleted

The pipelining option now defaults to False

Fixed SSL error for external DB

Added options for Ansible settings

Added support for external databases with SSL configuration

Added support for configuring UWSGI options in a separate settings file

Added options for service-to-host mapping

Added auto-scroll for the Jobs section

Implemented the ability to dynamically generate the list of action sub-actions

Reworked ADCM flags

Added logging of the client version to audit logs

Added options for removing admin user

Optimized the host creation operation

Fixed error related to removing hosts

Fixed issues related to displaying information regarding permissions

Fixed validation issues

Added the pattern attribute for string-based types

Separated logic for working with ADCM objects and Ansible

Optimized logic for the status server

Reworked API v2 schema

Reworked statistics service

This version of ADCM does not support ET prior to v2024070400

Fine-tune LDAP stability

Fixed migration error related to the ui_options field

Fixed config group name conflicts across clusters

Fixed LDAP authentication error by updating the user search base

Introduced a user blocking feature

Enhanced LDAP integration and permissions management

Added a new UI loading tool

Implemented a bulk operation for adding hosts to a cluster

Enhanced the display logic for Ansible logs

Refactored inventory generation

Implemented idempotence in the adcm_config module

Fixed an IPv6 issue

Fixed an error occurring during the upgrade of SSH bundles

Fixed an error when adding a duplicate host to a configuration group

Fixed an error during configuration posting via API v2

Enhanced security by ensuring that only superusers can view LDAP-related tasks

Fixed an error when saving a host-component mapping with duplicate links

Fixed unauthorized changes to maintenance mode for services and components

Resolved an issue that prevented the removal of a user from all groups via the API

Fixed an error encountered when posting imports twice

New UI is introduced

ADCM Auditor role is added

ADCM API 2.0 is now recommended for production use

Functionality for failed user login attempts reset has been upgraded to user unblocking

Improved performance of adding a service. Now this operation includes bulk operation logic

ADCM versioning rule is changed. The new version is 2.0.0

Login length in audit records is limited to 150 characters

Audit module log level is set to INFO

IP addresses collection in audit logs is supported

Requirement for invisible fields within structure is removed

The issue caused by non-unique names during termination of an action run is resolved

Bundle signature check mechanism is implemented

Added an optional feature for aggregating non-sensitive cluster details

API v2 initial release is supported. Since it is in the alpha phase, note that its features may undergo further adjustments. API v2 is not yet recommended for use in production environments. For more information, please refer to the documentation

Role-based access model is based on groups instead of users

adcm_config does not work with the integer data type

required import issues depend on the order in which they are declared

file and secretfile types do not work for action configs

Action run stops when the before upgrade field is generated in the inventory

It is not possible to manually tick the ADCM Administrator checkbox for an LDAP user

Adding invisible fields is implemented for the structure config parameter type

config_jinja is supported for the task action type

Passing NonType (null) to inventory instead of an empty map configuration parameter

Incorrect variables in inventory for the *.maintenance_mode groups if the host is not added to the configuration group

License does not show up during bundle upgrade

adcm_hostid and other variables are missing when a host is placed in Maintenance Mode

VM initialisation does not start due to the six package being absent

Brute-force protection mechanism is implemented

Password policy is changed

RBAC functionality is improved

Variables defined in the CLUSTER group are not available for a host in maintenance mode

Wrong order of objects on the Hosts - Components page

The Hosts - Components page is not updated in case of reverting an upgrade

500 error when trying to upload a bundle that contains similar action names

Wrong order of actions within a job

Host in maintenance mode is not included in target

Different event identifiers for SQLite and PostgreSQL

Empty configuration parameter cannot be saved in a configuration group

Database errors after ADCM upgrade

Gateway timeout error after adding a new policy

Service dependency mechanism is implemented

display_name is added for upgrades

Added ability to commit changes in hc_map during an operation being executed

Added ability to manage activatable group state via adcm_config

Added ability to access previous parameters during the upgrade

Prolonged update procedure for a cluster with RBAC policy

Incorrect order of starting subactions within actions

Ability to use an external database to store metadata is added

Data migration from SQLite to PostgreSQL is supported. PostgreSQL database is recommended for use in the product environment. SQLite database is intended for experimental purposes

Time taken to switch maintenance mode on and off is reduced

Time taken to save configs and config groups is reduced

ADCM documentation link is updated

Django is updated to the latest version (3.2)

Bell icon user experience is improved

Critical error on the server when a user logs in via LDAP

Incorrect inheritance of maintenance mode

Unable to remove a component from the host in maintenance mode

Empty list shows when the last item is deleted from the second or further page

Trash button gives the SERVICE_CONFLICT error if the service has binded imports

Job is not terminated after a cluster is deleted

Some of the UI elements for hostproviders are broken

Save page for the components map freezes

Component concern link leads to the wrong page

Adding a policy leads to a gateway-timeout error during every ADCM operation

Cluster concern event is not sent when the cluster is created

500 error when trying to terminate a process that is already stopped

Ask for help button leads to the outdated link

Required message for empty fields does not show at all times it should

Group config cannot be saved if a field is changed

Error in URL when a job is selected via the bell button

Expected service concerns are not displayed in the menu at the left side

Config group parameter values are not synchronized between different inventory host groups

Bell icon does not react to events that arrive from backend

Bundle downgrade mechanism is implemented

License agreement confirmation mechanism is implemented for services

Mechanism for dynamic generation of configs is implemented for actions

secretfile config parameter type is added

secretmap config parameter type is added

skip option (allow_to_terminate) is added for subactions

The ability to set the password and secrettext config parameters to empty

Column sorting does not work properly

Lists of cluster and hostprovider bundles have duplicated entries after cluster or hostprovider is created

The ability to rename a cluster without recreating the object from scratch

The download functionality is implemented for action logs

The maintenance mode is implemented for services and components

The ability to view audit logs via UI

The status aggregation logic is improved according to service/component statuses

Ansible is upgraded to 2.9.27

The ability to map the Maintenance mode button to an action

The ability to map the Trash service removal button to an action

LDAP Sync action does not synchronize all users

When a job is stopped, the stderr and stdout files are blank

Filters for groups in ADCM LDAP integration settings do not work for users in those groups

When a bundle is uploaded, there is an error of the action name being too long

Change the name of the link to hostprovider at the HOSTS tab

Issue does not disappear after a cluster is upgraded

The ability to forward the display name of services and components in inventory

The ability to generate logs in CEF format is added to support the security audit functionality

The user deactivation functionality is substituted for user deletion

The ability to generate inventory host groups for hosts in maintenance mode is added

The ability to rename clusters and hosts via API

The ability to download action logs in bulk via API

UI: several fixes in group-config

Backend: the 500 error when launching action with config parameter that is able to be activated

Backend: the 500 error when uploading bundles with similar upgrade names

Backend: the CLUSTER_SERVICE_NOT_FOUND error in the JOBS page when pagination size equals 50 or 100

Backend: the config parameters of different objects are not synchronized across config groups

Backend: the service delete functionality works regardless of state

Backend: the config group customization does not affect the service/component configuration

UI: the concern link leads to the object details page, yet not to the page with the concern owner

The user authentication via Active Directory/LDAP is supported

The multiphase bundle upgrade functionality is added

The ability to remove deprecated components and services during upgrade is added

Backend: the brackets are not allowed in the upgrade name in case of pre/post-logic used

Backend: the spaces are not allowed in the bundle name in case of upgrade pre/post-logic used

Backend: the inability to save a group config containing an empty parameter of a list type

Backend: the passwords in ADCM logs are unmasked

The maintenance mode is supported for hosts

The support of group config for parameter types that are able to be activated is added

The ability to remove services that are in the created state is added

UI: the possibility to include the configuration field in the group-config in case of config_group_customization=False, advanced: true, and not only

Fixed: the inability to save configuration if component is not selected within the constraint of [0, odd]

Backend: the service configuration group ignores the configuration and presence of collocated services

Backend: the 500 error is received when launching action

Backend: expand on the locked hosts

Backend: the GROUP_CONFIG_CHANGE_UNSELECTED_FIELD error

Backend: the group configuration changes are not saved after the Save button is clicked

UI: the group configuration field should be enabled

The multiphase bundle upgrade functionality is added

The Mitogen support is disabled

The support of static jinja2 files during the bundle build is added for ADCMClient

Backend: fix the Ansible service_facts module

Backend: missing Ansible Vault secrets when importing/exporting clusters

The filtering of clusters, services, hosts, and hostproviders according to access rights

The filtering of object’s actions and their task logs according to access rights is implemented for backend

Multiple vulnerabilities eliminated (CVE)

Fixed: the weblinks are displayed incorrectly

Backend: optimize the policy application algorithm

Backend: the default value of the read-only configuration parameters does not change after the bundle upgrade

Backend: the database is locked when the bundle is uploaded during the cluster installation

Backend: Internal server error occurs when navigating to the JOBS tab

Backend: the min > max import range allows to upload a bundle and make an import as if it was the max > min import range

UI: turn off route redirection if permissions are denied

The RBAC functionality is added

Ansible 2.9 is supported (as an alternative) for SDK

The previous cluster state is enabled during upgrade

The abort job functionality is enabled after deleting an object

The date, time, and log level are included in the adcm_debug.log file

Fixed: some bugs related to the group-configs

Backend: the configuration parameters file resets to the file path instead of the file value

Backend: the endless job after a cluster is deleted

Backend: the service component is losing its own configuration during upgrade

Backend: the inability to start a host action

Backend: the import from another object of the same bundle is forbidden

UI: the broken links on the JOBS tab

UI: the Back button does not work on the JOBS tab

UI: the job that is in progress does not refresh the bell icon

UI: the failed jobs are shown before the succeeded ones under the bell icon

UI: the default values for the list and map types are displayed instead of the current values