https://github.com/googleapis/google-cloud-cpp/tree/main/google/cloud/storage/emulator contains an emulator for GCS written in python. It is used by this project, but I believe it's also used by other projects as well (or will be soon? maybe someone can correct me if I'm wrong). The owners of this repo (@googleapis/cloud-cxx-owners) do not actually own or work on this code, may not be python experts, and may not be the right people to troubleshoot issues w/ this code.
I think we probably want to move google/cloud/storage/emulator/... to a separate repo.
Who will own the new repo? Not sure, but I'd look to @frankyn to either own it or help identify appropriate owner(s).
How will we (and others) access the emulator? Do other teams use it today out of this repo today? How do they do that? Maybe we can continue doing that. Or maybe it can be published in a docker image, or as a pip module, or add it to gcloud alpha emulators.
When should this happen? There's no urgency, but I'd say now would work. Later would work too if now is booked.
What should move? All the (python) emulator code in https://github.com/googleapis/google-cloud-cpp/tree/main/google/cloud/storage/emulator
Thoughts? @frankyn @coryan Feel free to add others who you think might have opinions.
https://github.com/googleapis/google-cloud-cpp/tree/main/google/cloud/storage/emulator contains an emulator for GCS written in python. It is used by this project, but I believe it's also used by other projects as well (or will be soon? maybe someone can correct me if I'm wrong). The owners of this repo (
@googleapis/cloud-cxx-owners) do not actually own or work on this code, may not be python experts, and may not be the right people to troubleshoot issues w/ this code.I think we probably want to move
google/cloud/storage/emulator/...to a separate repo.Who will own the new repo? Not sure, but I'd look to @frankyn to either own it or help identify appropriate owner(s).
How will we (and others) access the emulator? Do other teams use it today out of this repo today? How do they do that? Maybe we can continue doing that. Or maybe it can be published in a docker image, or as a pip module, or add it to
gcloud alpha emulators.When should this happen? There's no urgency, but I'd say now would work. Later would work too if now is booked.
What should move? All the (python) emulator code in https://github.com/googleapis/google-cloud-cpp/tree/main/google/cloud/storage/emulator
Thoughts? @frankyn @coryan Feel free to add others who you think might have opinions.