Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server: define an API to access tenant metadata from tenant servers #105721

Closed
knz opened this issue Jun 28, 2023 · 0 comments · Fixed by #105441
Closed

server: define an API to access tenant metadata from tenant servers #105721

knz opened this issue Jun 28, 2023 · 0 comments · Fixed by #105441
Assignees
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-multitenant Issues owned by the multi-tenant virtual team

Comments

@knz
Copy link
Contributor

knz commented Jun 28, 2023

Currently the SQL service is unable to inspect its own tenant metadata fields (e.g. tenant name, service mode).

We need to communicate these fields from the KV layer to the SQL pod on tenant server startup.

Epic: CRDB-26691

Jira issue: CRDB-29161

@knz knz added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-multitenancy Related to multi-tenancy labels Jun 28, 2023
@exalate-issue-sync exalate-issue-sync bot added A-multitenancy Related to multi-tenancy T-multitenant Issues owned by the multi-tenant virtual team and removed A-multitenancy Related to multi-tenancy T-multitenant Issues owned by the multi-tenant virtual team labels Jun 28, 2023
@craig craig bot closed this as completed in 68985a2 Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-multitenant Issues owned by the multi-tenant virtual team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant