The multipart-form upload API at POST /api/v2/collections
no longer needs form fields for 'name' and 'version', so
remove them and code needed to populate them.
Namespace,name, version are inferred server side from the filename
field in the form body. Currently nothing clever is done client
side to synthesize or generate that filename field if 'publish'
command is given a filename that is not of
the form 'namespace-name-1.2.3.tar.gz'.
Add a publish action unit test.
ISSUE TYPE
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
The multipart-form upload API at POST /api/v2/collections no longer needs form fields for 'name' and 'version', so remove them and code needed to populate them.
Namespace,name, version are inferred server side from the filename field in the form body. Currently nothing clever is done client side to synthesize or generate that filename field if 'publish' command is given a filename that is not of the form 'namespace-name-1.2.3.tar.gz'.
Add a publish action unit test.
ISSUE TYPE
MAZER VERSION
ADDITIONAL INFORMATION