Retrieve Galaxy api prefix when resource_provider is present #403
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
bmclaughlin
added a commit
to bmclaughlin/galaxy_collection
that referenced
this pull request
Jun 6, 2024
bmclaughlin
added a commit
to bmclaughlin/galaxy_collection
that referenced
this pull request
Jun 7, 2024
bmclaughlin
added a commit
to bmclaughlin/galaxy_collection
that referenced
this pull request
Jun 7, 2024
bmclaughlin
added a commit
to bmclaughlin/galaxy_collection
that referenced
this pull request
Jun 7, 2024
bmclaughlin
added a commit
to bmclaughlin/galaxy_collection
that referenced
this pull request
Jun 7, 2024
sean-m-sullivan
pushed a commit
that referenced
this pull request
Jun 7, 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.
What does this PR do?
Retrieves Galaxy api prefix when resource_provider is present, defaults to existing behavior.
How should this be tested?
Probably in the galaxy_ng repo by spinning up a new testing stack and running galaxy_collection test playbooks against it.
Is there a relevant Issue open for this?
None
Other Relevant info, PRs, etc
None