This document contains tips for existing users of Google Cloud Storage's deprecated v1beta2 beta release who would like to migrate to version v1. If you are new to Google Cloud Storage or its JSON API, you do not need to worry about this document.
The v1 release of the JSON API is nearly identical to v1beta2, the most recent limited availability release. However, there are some important differences that you should be aware of.
Contents
Migration Instructions
For existing users of JSON API v1beta2, upgrading to v1 is a straightforward task in most cases. Before doing so, please read the sections below documenting the changes from v1beta2.
Updating HTTP Calls
If you are constructing JSON-HTTP requests directly for this API, simply replace URLs beginning "https://www.googleapis.com/storage/v1beta2" with new URLs referencing the v1 path: "https://www.googleapis.com/storage/v1".
Updating Object Change Notifications
JSON API v1beta2 includes support for object change notifications , as does v1. However, incoming notification channels are associated with particular API versions. In order to ensure continued receipt of notifications after v1beta2 has been turned down, you will need to re-issue a watch request using the v1 API for buckets that currently have v1beta2 notification channels. Because code that listens for notifications already must handle the possibility of receiving duplicate notifications (see Reliable Delivery ), the following is the recommended procedure for performing this update:
-
Verify Your Compatibility
Verify that your system can handle v1 notification messages as well as duplicate messages correctly. This should already be the case, as existing notifications may be delivered multiple times, and the only change from v1beta2 to v1 messages are the URLs in the
X-Goog-Resource-Uri
header, theselfLink
property, and themediaLink
property. After sending a watch request to v1, you will also receive a v1 initial sync message.