Roll back a project's published Remote Config template to the one specified by the provided version number.
A rollback is equivalent to getting a previously published Remote Config template, and re-publishing it using a force update. Returns the published RemoteConfig and the updated ETag as a response header if successful, or an error.
See the publishing guide for a list of error codes. In particular, note that the method returns an error with HTTP Status 404 if the requested versionNumber
to rollback to is not found.
HTTP request
POST https://firebaseremoteconfig.googleapis.com/v1/{project=projects/*}/remoteConfig:rollback
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
project |
Required. The Firebase project's Project ID or Project Number, prefixed with "projects/". |
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "versionNumber": string } |
Fields | |
---|---|
versionNumber |
Required. The version number of the |
Response body
If successful, the response body contains an instance of RemoteConfig
.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/firebase.remoteconfig
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.