API key authentication - #8
Merged
Merged
Conversation
…uest header is valid, and if the API key is invalid
Member
|
Added two unit tests to test for if the auth implementation works if the API key is correct and incorrect. |
neagualexa
reviewed
Aug 11, 2025
neagualexa
left a comment
neagualexa
left a comment
There was a problem hiding this comment.
should the tests also cover HTTPS?
neagualexa
approved these changes
Aug 11, 2025
# Conflicts: # Dockerfile
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR implements API key authentication using the value provided in the
API_KEYheader with HTTP requests.The source API key can be provided using the
AUTH.KEYenvironment variable, or the--auth-keyCLI flag.