-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[v16] Adds support to Firestore backends for custom databases #47583
Merged
Conversation
This file contains 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
🤖 Vercel preview here: https://docs-c3763imls-goteleport.vercel.app/docs/ver/preview |
Firestore has supported multiple databases in a project for a while (see https://cloud.google.com/blog/products/databases/manage-multiple-firestore-databases-in-a-project), however, Teleport only allowed using the default database in the project. The DatabaseID is now exposed in the file config, and if provided both the state and events backends will use the appropriate database. Closes #37227.
rosstimothy
force-pushed
the
tross/backport-47540/v16
branch
from
October 15, 2024 17:50
d0d98a1
to
6b55122
Compare
🤖 Vercel preview here: https://docs-4brg8rnc1-goteleport.vercel.app/docs/ver/preview |
github-actions
bot
added
audit-log
Issues related to Teleports Audit Log
documentation
size/sm
labels
Oct 15, 2024
espadolini
approved these changes
Oct 15, 2024
zmb3
approved these changes
Oct 16, 2024
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 16, 2024
) Firestore has supported multiple databases in a project for a while (see https://cloud.google.com/blog/products/databases/manage-multiple-firestore-databases-in-a-project), however, Teleport only allowed using the default database in the project. The DatabaseID is now exposed in the file config, and if provided both the state and events backends will use the appropriate database. Closes #37227.
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Oct 16, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Oct 16, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Backport #47540 to branch/v16
Changelog: Allow using a custom database for Firestore backends.