Justin said it all very well.
On Tue, May 7, 2019 at 8:55 AM Brian Bouterse wrote:
> I was initially in favor of adopting the comma separated change, but
> reading @jsherril's response (which I agree with) I think straightened my
> thinking out. I think we should continue the escaping as is. We
I was initially in favor of adopting the comma separated change, but
reading @jsherril's response (which I agree with) I think straightened my
thinking out. I think we should continue the escaping as is. We shouldn't
change the API structure to support easier manual URL forming at the
expense of be
To me the API is the interface to pulp, not httpie and I do not think
you should corrupt the api to make it easier to use from httpie (I.e.
switch to using comma separated values when json provides a method for
specifying multiple values).
If you want to support both on the server I think that
Providing Pulp with lists of values from the command line is rather
unweildy. There's a lot of unnecessary escaping going on.
http POST :24817${REPO_HREF}versions/
add_content_units:="[\"$CONTENT_HREF\",\"$CONTENT_2_HREF\"]"
http POST http://localhost:24817/pulp/api/v3/rpm/copy/
source_repo=${SR
