Skip to content

fix: Eliminate use of user-tenants on tenant enablement#917

Draft
viacheslavkol wants to merge 4 commits intomasterfrom
MSEARCH-1116
Draft

fix: Eliminate use of user-tenants on tenant enablement#917
viacheslavkol wants to merge 4 commits intomasterfrom
MSEARCH-1116

Conversation

@viacheslavkol
Copy link
Contributor

@viacheslavkol viacheslavkol commented Mar 13, 2026

Purpose

Consortia is usually not set up during module for tenant enablement so module should not use consortia related calls during the enablement.
We already have tenant parameter check to validate if it's the member tenant of the consortium. In such case - simple tenant setup is executed. In case it's enablement of central tenant there're a few calls for languages and index creation that use user-tenant calls for determining the current tenant context f.e. if called from member - change to central, which is redundant since this functionality is not called for member. And for central this results in caching empty user-tenants call response.

Approach

Implement a version of a few services that doesn't account for consortia and doesn't change tenant context avoiding user-tenants calls and caching empty results. Set consortia beans as primary so general module functionality is not affected

Changes Checklist

  • API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
  • Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
  • Interface Version Changes: Indicate any changes to interface versions.
  • Interface Dependencies: Document added or removed dependencies.
  • Permissions: Document any changes to permissions.
  • Logging: Confirm that logging is appropriately handled.
  • Unit Testing: Confirm that changed classes were covered by unit tests.
  • Integration Testing: Confirm that changed logic was covered by integration tests.
  • Manual Testing: Confirm that changes were tested on local or dev environment.
  • NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues

MSEARCH-1116

@viacheslavkol viacheslavkol self-assigned this Mar 13, 2026
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant