fix: Eliminate use of user-tenants on tenant enablement#917
Draft
viacheslavkol wants to merge 4 commits intomasterfrom
Draft
fix: Eliminate use of user-tenants on tenant enablement#917viacheslavkol wants to merge 4 commits intomasterfrom
viacheslavkol wants to merge 4 commits intomasterfrom
Conversation
…ntId parameter instead for all tenant-dependant calls
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



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
Related Issues
MSEARCH-1116