Skip to content

Conversation

maryiaLichko
Copy link
Contributor

@maryiaLichko maryiaLichko commented Sep 9, 2025

Added TCM release topics to the toc-tree + general info

  • 1.3
  • 1.4
  • 1.5

Doc ticket: https://jira.vk.team/browse/TNTP-4444

Deployment: https://docs.d.tarantool.io/ru/doc/doc-tcm-releases/tooling/tcm/tcm_releases/

@maryiaLichko maryiaLichko self-assigned this Sep 9, 2025
@maryiaLichko maryiaLichko added release-notes Writing and editing release notes TCM labels Sep 9, 2025
@maryiaLichko maryiaLichko changed the title doc: tcm release files added (toc tree, general) doc: tcm update releases Sep 9, 2025
@github-actions github-actions bot temporarily deployed to branch-doc-tcm-releases September 9, 2025 13:54 Destroyed
@github-actions github-actions bot temporarily deployed to branch-doc-tcm-releases September 9, 2025 14:37 Destroyed
@github-actions github-actions bot temporarily deployed to branch-doc-tcm-releases September 9, 2025 14:41 Destroyed
@github-actions github-actions bot temporarily deployed to branch-doc-tcm-releases September 9, 2025 14:59 Destroyed
@github-actions github-actions bot temporarily deployed to branch-doc-tcm-releases September 9, 2025 15:09 Destroyed

Latest release in series: 1.3.1

|tcm_full_name| 1.3.0 enhances the TCF integration page with minor bug fixes and functional enhancements.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

functional enhancements -> functional improvements.
(mostly because lower we speak of improvements)

Starting from version 1.3.0, |tcm| provides additional actions for managing TCF clusters through the web interface.
You can now use **promote** and **demote** operations directly on the **TCF** page without switching to external tools.
Also, the **TCF** page is now disabled by default and must be explicitly enabled if needed.
In addition, |tcm| now supports connections to multiple gRPS servers, which improves integration with distributed cluster infrastructures.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gRPS servers -> gRPC servers?


The LDAP configuration form has been simplified:

* ``groupQueryTemplate`` field is now optional, allowing LDAP authentication without querying for user groups.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The groupQueryTemplate field

The LDAP configuration form has been simplified:

* ``groupQueryTemplate`` field is now optional, allowing LDAP authentication without querying for user groups.
* ``queryUser`` and ``queryPassword`` fields are also optional, which enables anonymous binding to the LDAP server.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The queryUser and queryPassword fields

- CRUD and Explorer -- data types used during operations have been corrected to comply with FSTEC security requirements, ensuring strict typing and better protection of sensitive data.
- Authentication -- the system no longer relies on etcd for storing authentication parameters. Instead, it uses local configuration to improve startup reliability and simplify setup.
- Logging -- fixed issues with log output by switching to the ``slog`` logging system.
- UI -- resolved display issues in the ``OperationStatus ``component.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OperationStatus component -> OperationStatus component

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes Writing and editing release notes TCM
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants