Publish a project's Remote Config template.
Pass the ETag returned by projects.getRemoteConfig as an If-Match header to ensure the last seen Remote Config template is the one being overwritten by this update. Pass If-Match: * to force an update, regardless of the current version.
Returns the published RemoteConfig and the updated ETag as a response header if successful, or an error.
To update the server-side template, use "firebase-server" as the namespace ID in [UpdateRemoteConfigRequest.name]. If [UpdateRemoteConfigRequest.name] is not provided, the client-side template ('firebase' namespace) is updated.
See the publishing guide for a list of error codes.
HTTP request
PUT https://firebaseremoteconfig.googleapis.com/v1/{project=projects/*}/remoteConfig
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
project |
The Firebase project's Project ID or Project Number, prefixed with "projects/". This field is required if the |
Query parameters
| Parameters | |
|---|---|
validateOnly |
Optional. Defaults to Note: other errors may still occur after this boolean is set to |
name |
Optional. The name of the RemoteConfig to update. 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 an instance of RemoteConfig.
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 OAuth 2.0 Overview.