-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kvtenant: move kv tenant connector out of ccl #98226
Copy link
Copy link
Closed
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual teamv23.1.2
Description
We want to move the KV tenant connector out of kvtenantccl to kvtenant to enable wider test coverage of multi-tenant features. There should be two ways to instantiate the connector. A connector that connects to any supplied addresses and a connector that only connects to a loopback address.
Existing multi-tenant capable tests that reference the ccl package should be updated to use the appropriate connector, whether it be a connector that can connect only via loopback or one that can connect to remote nodes.
Epic: CRDB-16091
Jira issue: CRDB-25139
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual teamv23.1.2