-
Notifications
You must be signed in to change notification settings - Fork 2k
build: enable cloud build for healthcare/dicom #2316
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
Conversation
| process.env.GOOGLE_APPLICATION_CREDENTIALS, | ||
| 'Must set GOOGLE_APPLICATION_CREDENTIALS environment variable!' | ||
| ); | ||
| projectId = await storage.getProjectId(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this storage.getProjectId() just because the Storage client is being used in this file? As opposed to google.auth.getProjectId().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, it calls the same underlying method. I used storage.getProjectId() because we already had a storage client, and it just exposes the underlying auth method. This method is available on all client libraries.
|
@JustinBeckwith any reason we can't merge this? seems to have run the dicom test. We're currently blocking on this test here. |
|
@bcoe this PR shouldn't be blocking anything - I am guessing that's a result of Cloud Build not re-running the trigger after the branch transition. I am guessing that pushing to that other branch any change will kickstart the cloud build job. That having been said, we could totally merge this now with no side effects. |
* do not merge: poke dicom test * boop * make tests more pliable * huh?
No description provided.