Repository navigation
Enable Compute Engine API for system tests project #816
Description
@jgeewax I merged support for Compute Engine, but didn't realize our tests project would have to enable it:
Uncaught Error: Access Not Configured. The API (Compute Engine API) is not enabled for your project. Please use the Google Developers Console to update your configuration.
I know leaving extra resources lying around isn't a good idea with GCE. Here's the philosophy of how our system tests work: https://github.com/GoogleCloudPlatform/gcloud-node/blob/f10000f44cb8646558ea5e255db88720a595af70/system-test/compute.js#L11
If you don't want to enable it, I can come up with a way to shut off the tests conditionally. Otherwise, just let me know when it's flipped on and I'll do a release to get the GCE greatness out to the masses.
Metadata
Metadata
Assignees
Labels
No labels
Activity
jgeewax commentedon Aug 21, 2015
Enabled. Check if that worked and close out if so @stephenplusplus ?
stephenplusplus commentedon Aug 21, 2015
We're green 👍 Thanks!
fix(deps): update dependency @google-cloud/vision to v3 (#816)
chore(main): release 7.0.3 (#817)
chore(deps): update dependency sinon to v11 (#816)
build: updates to publish and devsite scripts (#816)
chore(cloud-rad): delete api-extractor config (#816)
chore(cloud-rad): delete api-extractor config (#816)
fix: return operation array from getOperation method (#816)
build: missing closing paren in publish script (#816)
test: remove tls for benchwrapper (#816)
fix: enum, bytes, and Long types now accept strings (#816)
fix: include long import in proto typescript declaration file (#816)
chore(main): release 5.0.2 (#816)
test: remove tls for benchwrapper (googleapis#816)
chore: release 3.2.0 (#816)
chore: release 3.2.0 (#816)
chore: release 3.2.0 (#816)
chore: release 3.2.0 (googleapis#816)