-
Notifications
You must be signed in to change notification settings - Fork 367
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
Cloud Storage with local emulator #18
Comments
From @stephenplusplus on October 20, 2016 19:52 Can you link the mock libraries? I'm not sure they'd be the same, but soon we will support using a custom endpoint which accepts the requests from our API (#1630). |
From @arbesfeld on October 20, 2016 19:54 Here are a few : |
I don't anticipate having an official solution for this. For offline development, you can use any HTTP request interceptor library that may exist. You can see the endpoints we hit in the source code, and if you want to log all of them: const Storage = require('@google-cloud/storage')
const gcs = new Storage()
gcs.interceptors.push({
request: reqOpts => {
console.log(reqOpts)
return reqOpts
}
}) This will log all HTTP requests we make in the format the Also, if you pass const Storage = require('@google-cloud/storage')
const gcs = new Storage({ customEndpoint: true }) Hopefully this is helpful. Feel free to ask any questions. |
From @arbesfeld on October 20, 2016 19:50
There are a few "Mock s3" servers that run in memory/disk. Since the google cloud storage and S3 APIs are the same, I was wondering if there was a way to use one of these servers with the Cloud Storage client? If not, what is the recommended way to use this API for local development?
Copied from original issue: googleapis/google-cloud-node#1731
The text was updated successfully, but these errors were encountered: