Open
Description
Wit the introduction of hierarchies #132, we introduced a new constraint to creating new resources. They'll often need to have a parent set. The CLI should have some way of handling this in the new command.
We have a couple of approaches:
Skip the parent, let the server decide
This is the current situation. Atomic-Server sets a default parent if none is included in the commit. Downsides of this, is that the Agent requires root write rights (to the base URL), and that it is not possible to set a resource under some other parent in the first action.
Add a flag
Easy enough, right?
Default to collection / find default collection
Perhaps the CLI should identify what the default collection is for this server, and should commit to there?
Or maybe this should be server responsibility...
EDIT: the server does this, defaults to base URL (Drive)