v0.18.0
Updating
$ npm update gcloud
Breaking Changes
No more apiResponse
in dataset.get
When getting entities from your dataset, the upstream API sometimes forces us to make multiple requests before returning all of the results. We do this for you automatically, but when going over this method recently, we noticed we were returning an apiResponse
value. That can be misleading, as if we had to make multiple requests, apiResponse
would only have been the last one.
To match our convention in other places within our API, anytime there is a possibility for multiple requests, we don't provide an apiResponse
. If you previously depended on it, please update your code accordingly. If that's not possible, please open an issue so we can learn more about your use case and help find a solution.
Introductions
Hello, Cloud DNS! (#486, #706)
This release introduces support for Google Cloud DNS.
Google Cloud DNS is a high-performance, resilient, global DNS service that provides a cost-effective way to make your applications and services available to your users. This programmable, authoritative DNS service can be used to easily publish and manage DNS records using the same infrastructure relied upon by Google.
Example: Creating an NS record
var dns = gcloud.dns({
keyFilename: '/path/to/keyfile.json',
projectId: 'my-project'
});
var zone = dns.zone('my-existing-zone');
var nsRecord = zone.record('ns', {
ttl: 86400,
name: 'my-domain.com.',
data: 'ns-cloud1.googledomains.com.'
});
zone.addRecord(nsRecord, function(err, change) {});
Documentation
We're always working to improve our documentation. Since the last release, among various smaller changes, we also have 4 revamped guides, covering the topics:
Fixes
- Core (#785): Handle unexpected network errors.
Features
- Datastore (#750 (comment), #755): Support streaming
dataset.get()
operations.
Thank you!
Thanks to you, we continue to fix, tweak, and grow our library. If you have ideas how we can improve, please let us know. See our new Contributing guide for how to get started.