v3: Drop support for legacy_api_key_v1 #999
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
psrok1
force-pushed
the
drop/legacy-api-key-v1
branch
2 times, most recently
from
df84f51 to
e0ab5f4
Compare
psrok1
force-pushed
the
drop/legacy-api-key-v1
branch
from
e0ab5f4 to
e50b606
Compare
psrok1
added a commit
that referenced
this pull request
Dec 16, 2024
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.
Your checklist for this pull request
[ ] I've added automated tests for my change (if applicable, optional)What is the current behaviour?
Legacy APi keys are deprecated since the initial v2 release, but was used by some mwdb.cert.pl users. Right now it's not even documented in the current API. Back in time, they were generated manually for early users of mwdb.cert.pl by admin using special script.
What is the new behaviour?
This PR removes support for legacy API keys (v1)