-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GoogleJSON directories#get does not accept a prefix option #296
Comments
I think the fact that worked before is a bug in the xml code. I would expect the call to be connection.directories.get(dir.key).files(prefix: prefix) For example the list call for files supports prefix in both APIs: https://cloud.google.com/storage/docs/json_api/v1/objects/list and https://cloud.google.com/storage/docs/xml-api/get-bucket-list |
Hmm that's interesting. We'll test out calling it that way with |
👍 |
It actually looks like we can't pass any arguments to
fog-google/lib/fog/storage/google_json/models/directory.rb Lines 40 to 47 in 4647ce1
The |
Thanks for re-opening the issue @erjohnso. Let us know if you need any other information that will help with debugging this issue. @elenasharma and I are taking this over from @tcdowney, so feel free to tag us directly as well. Thanks, |
@anniesing I've merged in @emilymye's PR with a fix, please give it a try. |
@icco Thank you, everything seems to work great now. When will the next release be cut? |
I'll cut now, was just waiting for someone to verify :D |
@icco 👏 👏 👏 👏 👏 |
In the older GoogleXML implementation you could pass this call a
prefix
option that would only fetch objects in the bucket that began with that prefix.For example, this would only return objects directly under the
06824f8f-d185-409f-be75-55dba0a9a904
directory:The newer API implementation no longer accepts
prefix
.fog-google/lib/fog/storage/google_json/models/directories.rb
Line 12 in 2d8da68
Is there a way that support for the
prefix
option could be maintained?Thanks!
Tim Downey && @maryamklabib
The text was updated successfully, but these errors were encountered: