Download semantics for Files about rack HOT 7 CLOSED

As I think about this with @rgbkrk I feel like --download is a better option. It will never surprise you when the option is explicit even though it requires more typing.

from rack.

Do we assume stdout or a download in these cases?

I could see myself using

rack files my-container log1.txt --download | grep "500 Internal Server Error"

from rack.

The problem I'm having with that syntax is that it's not consistent with the other services. Currently, we have a rack <service> <subservice> <action> <flags> format.
To stay consistent, It'd need to be something like:
rack files object download --container <containerName> --object <objectName>
Or possibly arguments instead of flags.

from rack.

I like it from a consistency standpoint ( @jrperritt ) but it does add a significant amount of typing. Perhaps it's worth it?

from rack.

There's not really a subservice on cloudfiles is there? Also, object confuses, for me, the access of a single object vs a container. This would come out as:

rack files object list --container <containerName>

from rack.

Would rack files container list make more sense?

from rack.

Closing for now. This has been implemented. Comment and/or re-open to to continue discussion.

from rack.