Skip to content

Provide an in-memory or local-disk emulator of the storage APIs for testing #684

Closed

Description

@dimo414

Easy to describe, hard to do :) Presently the only way I can verify my gcloud-java code is to run it against a real GCS bucket, which costs money and requires being authenticated.

Activity

  1. changed the title [-]Provide an in-memory or local-disk emulatior of the storage APIs for testing[/-] [+]Provide an in-memory or local-disk emulator of the storage APIs for testing[/+] on Feb 29, 2016
  2. aozarov commented on Feb 29, 2016

    @aozarov
    Contributor

    @dimo414 I completely agree!

    It is fairly simple to write something to support basic functionality (get/set/listing without options) but not so if we care about being a 100% (or close to it) compatible.

    It is on our road-map and in fact as part of the efforts to add nio.Files facade to GCS in gcloud-java-contrib (currently at the gcs-nio branch) we also plan to provide a basic local gcs implementation. Any contribution to make it better (and closer to the real service) are welcome!

    A different and complete local implementation that will be included in the cloud SDK will come at some point (but probably not any time soon).

    /cc @mziccard @jart @jean-philippe-martin

  3. dimo414 commented on Feb 29, 2016

    @dimo414
    Author

    Thanks @aozarov, an nio.Files facade will be excellent.

  4. jean-philippe-martin commented on Apr 25, 2017

    @jean-philippe-martin

    I believe this issue is related to #1993, which was just closed. We now expose a "LocalStorageHelper" that offers an in-memory emulator of (the core parts of) the storage API.

  5. garrettjonesgoogle commented on Jul 18, 2017

    @garrettjonesgoogle
    Contributor

    This is done, so closing out the issue.

  6. 3 remaining items

  7. added a commit that references this issue on Aug 9, 2022
  8. added a commit that references this issue on Oct 4, 2022
  9. added a commit that references this issue on Mar 30, 2026
  10. added a commit that references this issue on Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions