Method: projects.namespaces.remoteConfig.rollback

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.

To roll back the server-side template, use "firebase-server" as the namespace ID in [RollbackRemoteConfigRequest.name]. If [RollbackRemoteConfigRequest.name] is not provided, the client-side template ('firebase' namespace) is rolled back.

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/{name=projects/*/namespaces/*/remoteConfig}:rollback

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
name

string

Optional. The name of the RemoteConfig to rollback. Format: projects/{project}/namespaces/{namespace}/remoteConfig Project is a Firebase project ID or project number. Namespace is the namespace ID (e.g.: firebase or firebase-server)

Request body

The request body contains data with the following structure:

JSON representation 
{
  "project": string,
  "versionNumber": string
}
Fields
project

string

The Firebase project's Project ID or Project Number, prefixed with "projects/". This field is required if the name field is not provided.
versionNumber

string (int64 format)

Required. The version number of the RemoteConfig to roll back to. The specified version number must be less than the current version number, and not have been deleted due to staleness.

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 OAuth 2.0 Overview.