Add AuthToken.API_KEY SQL ENUM
#3398
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
PBENCH-1136 Stage one: this doesn't fix the API key encryption problem (Nikhil is working on that), but this adds the missing SQL ENUM value. Rather than creating a new Alembic revision file (which would be the normal process) I decided to keep this simple by updating the general API KEY revision file. As we have no database deployments we'll need to upgrade over this period, this strategy avoids adding another revision to the tree.
npalaska
approved these changes
Apr 25, 2023
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.
PBENCH-1136
Stage one: this doesn't fix the API key encryption problem (Nikhil is working on that), but this adds the missing SQL ENUM value.
Rather than creating a new Alembic revision file (which would be the normal process) I decided to keep this simple by updating the general API KEY revision file. As we have no database deployments we'll need to upgrade over this period, this strategy avoids adding another revision to the tree.