This is a sketch of supporting the /api/v2/collections API and removing
the use of /api/v2/repositories API.
This includes:
add entry points for the API endpoints to ansible_galaxy.rest_api.GalaxyAPI
updating ansible_galaxy.fetch.galaxy_url to be collections centric and use the collections API
removing various fiddly version compare code paths that previously had to deal with a mix of semver style versions and 'v1.2.3' style versions.
removing some download url guessing code that was previously based on Repository 'external_url' and sometimes just guessing at github style archive urls
GalaxyAPI.* methods renamed to kind of sort of reflect the names of the Galaxy server views they use (ie, get_collection_detail() and get_collection_version_list())
some tweaks to internals of GalaxyAPI
unit tests updates for the new API (and some stuff that was kind of wrong since the change to use 'requests')
Note: As of 2019-04-15, the galaxy side of (most) of /api/v2/collections API doesn't exist,
so this branch doesn't work at the moment.
Fixes: #216
ISSUE TYPE
Feature Pull Request
Bugfix Pull Request
MAZER VERSION
name = mazer
version = 0.4.0
config_file = /home/adrian/.ansible/mazer.yml
uname = Linux, newswoop, 5.0.5-200.fc29.x86_64, #1 SMP Wed Mar 27 20:58:04 UTC 2019, x86_64
executable_location = /home/adrian/venvs/mazer040test/bin/mazer
python_version = 3.6.8 (default, Jan 27 2019, 09:00:23) [GCC 8.2.1 20181215 (Red Hat 8.2.1-6)]
python_executable = /home/adrian/venvs/mazer040test/bin/python
SUMMARY
This is a sketch of supporting the /api/v2/collections API and removing the use of /api/v2/repositories API.
This includes:
Note: As of 2019-04-15, the galaxy side of (most) of /api/v2/collections API doesn't exist, so this branch doesn't work at the moment.
Fixes: #216
ISSUE TYPE
MAZER VERSION
ADDITIONAL INFORMATION