AAI-229 integrate Galaxy API into backend#28
Merged
Merged
Conversation
amandazhuyilan
approved these changes
Jun 13, 2025
amandazhuyilan
left a comment
amandazhuyilan
left a comment
Contributor
There was a problem hiding this comment.
Looks great! Thanks for the change!
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
2 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.
Description
AAI-229: add a Galaxy API key so we can fetch info from the Galaxy server. As an initial example, check if a username already exists in Galaxy, to prevent conflicts
Changes
Checklist
How to Test Manually (if necessary)
Run
uv run pytest