Closed andreaturli closed 11 years ago
I'd add in at least one api command, such as list buckets, and trim domain classes that are not yet referenced for later pull requests.
@adriancole I've added BucketApi with CRUD to have a meaningful LiveTest.
Still reviewing, do not merge until i've fully reviewed.
Code style seems off
Please fix the formatting and resubmit.
@mattstep wrt your comment on GoogleCloudStorageConstants, they are used in more than one place, so I think it makes sense to keep them separated.
Constants belong in organized places, having a "dump all" class for constants is useless. Find a good home for them so that they can be shared across classes. "Constants" is not a good home.
choosing to close this one out as folks at google suggest the XML api is the encouraged and supported binding. https://developers.google.com/storage/docs/developer-guide
I suspect most of this code could be renamed and put to use as another api such as BigQuery https://developers.google.com/bigquery/docs/reference/v2/
This is an initial support Google Cloud Storage (GCS) JSON API.
To simplify the review process, this PR contains only the initial scaffolding of the GCS provider and some domain objects related to the buckets (with unit tests).
As I don't have enough rights on this repo, I can't explicitly assign reviewers. From IRC I know @mattstep @andrewgaul @adriancole should be interested on looking into it. Thanks!