We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I encountered an error which indicates that gcs is no longer a function when trying to leverage with Google Cloud Storage (gcs).
gcs
⚠️ : TypeError: gcs is not a function
From my quick investigation, you can fix it replacing the codes like below for the time being:
https://github.com/looker/lookerbot/blob/master/src/stores/google_cloud_store.ts
in line 5
// const gcs = require("@google-cloud/storage") const {Storage} = require("@google-cloud/storage")
in line 19
// const storage = gcs({ // credentials: process.env.GOOGLE_CLOUD_CREDENTIALS_JSON ? JSON.pa rse(process.env.GOOGLE_CLOUD_CREDENTIALS_JSON) : undefined, // projectId: process.env.GOOGLE_CLOUD_PROJECT, // }) const storage = new Storage({ credentials: process.env.GOOGLE_CLOUD_CREDENTIALS_JSON ? JSON.par se(process.env.GOOGLE_CLOUD_CREDENTIALS_JSON) : undefined, projectId: process.env.GOOGLE_CLOUD_PROJECT, })
Since I'm not sure this could be a permanent measure, just allow me to leave an issue instead of PR.
The text was updated successfully, but these errors were encountered:
Still have this error on my end via a heroku deployment.
Can functionality be confirmed?
Sorry, something went wrong.
No branches or pull requests
Hi, I encountered an error which indicates that
gcs
is no longer a function when trying to leverage with Google Cloud Storage (gcs).From my quick investigation, you can fix it replacing the codes like below for the time being:
https://github.com/looker/lookerbot/blob/master/src/stores/google_cloud_store.ts
in line 5
in line 19
Since I'm not sure this could be a permanent measure, just allow me to leave an issue instead of PR.
The text was updated successfully, but these errors were encountered: