Open jordanhendricks opened 6 years ago
The mmpu commands operating on specific multipart uploads take a uuid as input. If you are someone who needs to look at other account's multipart uploads frequently, the only easy way to look at another account's MPU is by querying the API directly:
mmpu
$ mget -q /jhendricks/uploads/9/94df8d4f-55a7-420b-9a74-3f531e2ecde0/state | json { "id": "94df8d4f-55a7-420b-9a74-3f531e2ecde0", "state": "created", "partsDirectory": "/jhendricks/uploads/9/94df8d4f-55a7-420b-9a74-3f531e2ecde0", "targetObject": "/jhendricks/stor/create-no-parts", "headers": { "durability-level": 2 }, "numCopies": 2 }
It would be much more convenient to do something like:
$ mmpu get /jhendricks/uploads/9/94df8d4f-55a7-420b-9a74-3f531e2ecde0
With the integration of joyent/node-manta#326, this is much easier to do than before.
This usage pattern is similar to what mjob provides.
mjob
The
mmpucommands operating on specific multipart uploads take a uuid as input. If you are someone who needs to look at other account's multipart uploads frequently, the only easy way to look at another account's MPU is by querying the API directly:It would be much more convenient to do something like:
With the integration of joyent/node-manta#326, this is much easier to do than before.
This usage pattern is similar to what
mjobprovides.