v1

latestOpenAPI 3.0.0Creative Commons Attribution 3.02026-07-1392432.3 KB
projects

Create 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.

post/v1/{+name}/releases

Path parameters

namestring required

Required. Resource name for the project which owns this Release. Format: projects/{project_id}

Request body

namestring

Required. Format: projects/{project_id}/releases/{release_id}

rulesetNamestring

Required. Name of the Ruleset referred to by this Release. The Ruleset must exist for the Release to be created.

createTimestring google-datetime

Output only. Time the release was created.

updateTimestring google-datetime

Output only. Time the release was updated.

Response

Successful response