ProjectsReleases
class ProjectsReleases extends Resource (View source)
The "releases" collection of methods.
Typical usage is:
$firebaserulesService = new Google\Service\FirebaseRules(...);
$releases = $firebaserulesService->projects_releases;
Methods
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. (releases.create)
Delete a Release
by resource name. (releases.delete)
Get the Release
executable to use when enforcing rules.
List the Release
values for a project. This list may optionally be filtered
by Release
name, Ruleset
name, TestSuite
name, or any combination
thereof. (releases.listProjectsReleases)
Update a Release
via PATCH. Only updates to ruleset_name
will be honored.
Details
Release
create(string $name, Release $postBody, array $optParams = [])
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. (releases.create)
FirebaserulesEmpty
delete(string $name, array $optParams = [])
Delete a Release
by resource name. (releases.delete)
Release
get(string $name, array $optParams = [])
Get a Release
by name. (releases.get)
GetReleaseExecutableResponse
getExecutable(string $name, array $optParams = [])
Get the Release
executable to use when enforcing rules.
(releases.getExecutable)
ListReleasesResponse
listProjectsReleases(string $name, array $optParams = [])
List the Release
values for a project. This list may optionally be filtered
by Release
name, Ruleset
name, TestSuite
name, or any combination
thereof. (releases.listProjectsReleases)
Release
patch(string $name, UpdateReleaseRequest $postBody, array $optParams = [])
Update 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. (releases.patch)