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.
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 releases.patch method.
HTTP request
POST https://firebaserules.googleapis.com/v1/{name=projects/*}/releases
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2021-06-30 UTC."],[],[],null,["# Method: projects.releases.create\n\n- [HTTP request](#body.HTTP_TEMPLATE)\n- [Path parameters](#body.PATH_PARAMETERS)\n- [Request body](#body.request_body)\n- [Response body](#body.response_body)\n- [Authorization Scopes](#body.aspect)\n- [Try it!](#try-it)\n\nCreate a `Release`.\n\nRelease 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.\n\nMore than one `Release` may be 'live' concurrently. Consider the following three `Release` names for `projects/foo` and the `Ruleset` to which they refer.\n\nRelease Name -\\\u003e Ruleset Name:\n\n- projects/foo/releases/prod -\\\u003e projects/foo/rulesets/uuid123\n- projects/foo/releases/prod/beta -\\\u003e projects/foo/rulesets/uuid123\n- projects/foo/releases/prod/v23 -\\\u003e projects/foo/rulesets/uuid456\n\nThe 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 [releases.patch](/docs/reference/rules/rest/v1/projects.releases/patch#google.firebase.rules.v1.FirebaseRulesService.UpdateRelease) method.\n\n### HTTP request\n\n`POST https://firebaserules.googleapis.com/v1/{name=projects/*}/releases`\n\nThe URL uses [gRPC Transcoding](https://google.aip.dev/127) syntax.\n\n### Path parameters\n\n| Parameters ||\n|--------|-------------------------------------------------------------------------------------------------------------|\n| `name` | `string` Required. Resource name for the project which owns this `Release`. Format: `projects/{project_id}` |\n\n### Request body\n\nThe request body contains an instance of [Release](/docs/reference/rules/rest/v1/projects.releases#Release).\n\n### Response body\n\nIf successful, the response body contains a newly created instance of [Release](/docs/reference/rules/rest/v1/projects.releases#Release).\n\n### Authorization Scopes\n\nRequires one of the following OAuth scopes:\n\n- `https://www.googleapis.com/auth/cloud-platform`\n- `https://www.googleapis.com/auth/firebase`\n\nFor more information, see the [Authentication Overview](https://cloud.google.com/docs/authentication/)."]]
