I would expect /tmp/img1 to contain the same string: "No redirection or local file specified for downloaded image data. Please specify a local file with --file to save downloaded image or redirect output to another source." (That's how things typically work.)
"""
The message says "No redirction [...] specified for downloaded image data. Please [...] redirect output to another source" So why do you expect that to not work? That makes no sense
---
Also, OpenStack uses SemVer, correct? SemVer says, and I quote,
"Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable."
I'm not saying I agree or that this is justification for breaking this behaviour on you unexpectedly, but, those are the rules by which OpenStack operates. If you want glanceclient to have a real guarantee of API stability, we need to release 1.0.0.
Two other points:
""" 4ec9-4e74- a1bd-30e33324be 80 > /tmp/img1
$ glance image-download 96ed6a3f-
I would expect /tmp/img1 to contain the same string: "No redirection or local file specified for downloaded image data. Please specify a local file with --file to save downloaded image or redirect output to another source." (That's how things typically work.)
"""
The message says "No redirction [...] specified for downloaded image data. Please [...] redirect output to another source" So why do you expect that to not work? That makes no sense
---
Also, OpenStack uses SemVer, correct? SemVer says, and I quote,
"Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable."
I'm not saying I agree or that this is justification for breaking this behaviour on you unexpectedly, but, those are the rules by which OpenStack operates. If you want glanceclient to have a real guarantee of API stability, we need to release 1.0.0.