Repository navigation
feat(everest): add client for database credentials - #14
Merged
Merged
Conversation
Signed-off-by: amh1k <abdulmoizx97@gmail.com>
Signed-off-by: amh1k <abdulmoizx97@gmail.com>
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
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.
Description
Adds an OpenEverest API client to retrieve connection details for a PostgreSQL instance using its registered Kubernetes cluster name, namespace, and instance name. These details will support the coordinator’s future runner credential setup.
Changes
Testing
Tests cover successful retrieval, authorization failures, missing targets, invalid or incomplete responses, upstream failures, body-read errors, timeouts, and cancellation.
Note
The client returns the credentials based on namespace, cluster and instance name. It currently does not have the functionality to only return PostgreSQL databases
Kubernetes Secret creation, Job execution, and benchmark API handlers remain separate work.
Closes #9