Skip to main content

releases

Overview

Namereleases
TypeResource
Idfirebase.firebaserules.releases

Fields

NameDatatypeDescription
namestringRequired. Format: projects/{project_id}/releases/{release_id}
createTimestringOutput only. Time the release was created.
rulesetNamestringRequired. Name of the Ruleset referred to by this Release. The Ruleset must exist for the Release to be created.
updateTimestringOutput only. Time the release was updated.

Methods

NameAccessible byRequired ParamsDescription
projects_releases_getSELECTprojectsId, releasesIdGet a Release by name.
projects_releases_listSELECTprojectsIdList the Release values for a project. This list may optionally be filtered by Release name, Ruleset name, TestSuite name, or any combination thereof.
projects_releases_createINSERTprojectsIdCreate a Release. Release names should reflect the developer's deployment practices. For example, the release name may include the environment name, application name, application version, or any other name meaningful to the developer. Once a Release refers to a Ruleset, the rules can be enforced by Firebase Rules-enabled services. More than one Release may be 'live' concurrently. Consider the following three Release names for projects/foo and the Ruleset to which they refer. Release Name -> Ruleset Name projects/foo/releases/prod -> projects/foo/rulesets/uuid123 projects/foo/releases/prod/beta -> projects/foo/rulesets/uuid123 * projects/foo/releases/prod/v23 -> projects/foo/rulesets/uuid456 The relationships reflect a Ruleset rollout in progress. The prod and prod/beta releases refer to the same Ruleset. However, prod/v23 refers to a new Ruleset. The Ruleset reference for a Release may be updated using the UpdateRelease method.
projects_releases_deleteDELETEprojectsId, releasesIdDelete a Release by resource name.
projects_releases_patchEXECprojectsId, releasesIdUpdate a Release via PATCH. Only updates to ruleset_name will be honored. Release rename is not supported. To create a Release use the CreateRelease method.