Fix galaxy url use everywhere when url is set in config. #63286
Merged
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.
SUMMARY
Fix galaxy url use everywhere when url is set in config.
In addition to trying the configured url (for ex, a migrated
'https://galaxy.ansible.com/') there is an attempt at that
URL with '/api' postpended.
If the extended URL works, update GalaxyAPI.api_server to
use the extended URL. Previously it only used it for finding
the API root info ('available_versions', etc)
ISSUE TYPE
COMPONENT NAME
ansible-galaxy
ADDITIONAL INFORMATION
If there is configuration (config file, env var, etc) that specify a galaxy server that
doesn't include the path to the galaxy API root, ansible-galaxy tries appending
a '/api/' to it. But it wasn't doing that for other calls.
Example config pointing at the imcomplete galaxy api URL, that is automatically
also tried with '/api/' appended to it.
Before:
After: