Method: projects.remoteConfig.rollback
Stay organized with collections
Save and categorize content based on your preferences.
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 |
string
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 |
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.remoteconfighttps://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-06-11 UTC.
[null,null,["Last updated 2024-06-11 UTC."],[],[],null,["# Method: projects.remoteConfig.rollback\n\nRoll back a project's published Remote Config template to the one specified by the provided version number.\n\nA 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.\n\nSee the publishing guide for a list of [error codes](/docs/remote-config/use-config-rest#step_5_publish_json_data_to_replace_data_in_the_service). In particular, note that the method returns an error with HTTP Status 404 if the requested [versionNumber](/docs/reference/remote-config/rest/v1/projects.remoteConfig/rollback#body.request_body.FIELDS.version_number) to rollback to is not found.\n\n### HTTP request\n\n`POST https://firebaseremoteconfig.googleapis.com/v1/{project=projects/*}/remoteConfig:rollback`\n\nThe URL uses [gRPC Transcoding](https://google.aip.dev/127) syntax.\n\n### Path parameters\n\n| Parameters ||\n|-----------|----------------------------------------------------------------------------------------------------|\n| `project` | `string` Required. The Firebase project's Project ID or Project Number, prefixed with \"projects/\". |\n\n### Request body\n\nThe request body contains data with the following structure:\n\n| JSON representation |\n|-------------------------------------|\n| ``` { \"versionNumber\": string } ``` |\n\n| Fields ||\n|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `versionNumber` | `string (`[int64](https://developers.google.com/discovery/v1/type-format)` format)` Required. The version number of the [RemoteConfig](/docs/reference/remote-config/rest/v1/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. |\n\n### Response body\n\nIf successful, the response body contains an instance of [RemoteConfig](/docs/reference/remote-config/rest/v1/RemoteConfig).\n\n### Authorization scopes\n\nRequires one of the following OAuth scopes:\n\n- `https://www.googleapis.com/auth/firebase.remoteconfig`\n- `https://www.googleapis.com/auth/cloud-platform`\n\nFor more information, see the [Authentication Overview](https://cloud.google.com/docs/authentication/)."]]
