This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
Key Value Table requires workspace ID #240
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this do
Key-Value pairs stored in the database require a related workspace ID.
Why are we doing this
Continuing the Kubernetes migration. Setting up a staging environment requires us to make things "multitenant".
Adding a
workspace_idtag to theKeyValueStoreis not the best way to handle the Retweeter feature, but it's a good enough workaround for now.How should this be tested
Modified tests; do they pass?
Migrations
Adding a required foreign_key to the KeyValueStore. Doing it in 3 stages as this table already has records:
Dependencies
n/a