docs: update generated docs (#1053)
Updates for both discovery docs and epydoc API Documentation
Fixes: #1049
diff --git a/docs/dyn/firebaserules_v1.projects.releases.html b/docs/dyn/firebaserules_v1.projects.releases.html
index 7492039..c838db1 100644
--- a/docs/dyn/firebaserules_v1.projects.releases.html
+++ b/docs/dyn/firebaserules_v1.projects.releases.html
@@ -75,8 +75,11 @@
<h1><a href="firebaserules_v1.html">Firebase Rules API</a> . <a href="firebaserules_v1.projects.html">projects</a> . <a href="firebaserules_v1.projects.releases.html">releases</a></h1>
<h2>Instance Methods</h2>
<p class="toc_element">
+ <code><a href="#close">close()</a></code></p>
+<p class="firstline">Close httplib2 connections.</p>
+<p class="toc_element">
<code><a href="#create">create(name, body=None, x__xgafv=None)</a></code></p>
-<p class="firstline">Create a `Release`.</p>
+<p class="firstline">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 table reflects the `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.</p>
<p class="toc_element">
<code><a href="#delete">delete(name, x__xgafv=None)</a></code></p>
<p class="firstline">Delete a `Release` by resource name.</p>
@@ -87,80 +90,35 @@
<code><a href="#getExecutable">getExecutable(name, executableVersion=None, x__xgafv=None)</a></code></p>
<p class="firstline">Get the `Release` executable to use when enforcing rules.</p>
<p class="toc_element">
- <code><a href="#list">list(name, filter=None, pageSize=None, pageToken=None, x__xgafv=None)</a></code></p>
-<p class="firstline">List the `Release` values for a project. This list may optionally be</p>
+ <code><a href="#list">list(name, pageToken=None, pageSize=None, filter=None, x__xgafv=None)</a></code></p>
+<p class="firstline">List the `Release` values for a project. This list may optionally be filtered by `Release` name, `Ruleset` name, `TestSuite` name, or any combination thereof.</p>
<p class="toc_element">
<code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
<p class="firstline">Retrieves the next page of results.</p>
<p class="toc_element">
<code><a href="#patch">patch(name, body=None, x__xgafv=None)</a></code></p>
-<p class="firstline">Update a `Release` via PATCH.</p>
+<p class="firstline">Update a `Release` via PATCH. Only updates to the `ruleset_name` and `test_suite_name` fields will be honored. `Release` rename is not supported. To create a `Release` use the CreateRelease method.</p>
<h3>Method Details</h3>
<div class="method">
+ <code class="details" id="close">close()</code>
+ <pre>Close httplib2 connections.</pre>
+</div>
+
+<div class="method">
<code class="details" id="create">create(name, body=None, x__xgafv=None)</code>
- <pre>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 table reflects the `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.
+ <pre>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 table reflects the `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.
Args:
- name: string, Resource name for the project which owns this `Release`.
-
-Format: `projects/{project_id}` (required)
+ name: string, Resource name for the project which owns this `Release`. Format: `projects/{project_id}` (required)
body: object, The request body.
The object takes the form of:
-{ # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a
- # `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
- "name": "A String", # Resource name for the `Release`.
- #
- # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
- # which affords developers a great deal of flexibility in mapping the name
- # to the style that best fits their existing development practices. For
- # example, a name could refer to an environment, an app, a version, or some
- # combination of three.
- #
- # In the table below, for the project name `projects/foo`, the following
- # relative release paths show how flat and structured names might be chosen
- # to match a desired development / deployment strategy.
- #
- # Use Case | Flat Name | Structured Name
- # -------------|---------------------|----------------
- # Environments | releases/qa | releases/qa
- # Apps | releases/app1_qa | releases/app1/qa
- # Versions | releases/app1_v2_qa | releases/app1/v2/qa
- #
- # The delimiter between the release name path elements can be almost anything
- # and it should work equally well with the release name list filter, but in
- # many ways the structured paths provide a clearer picture of the
- # relationship between `Release` instances.
- #
- # Format: `projects/{project_id}/releases/{release_id}`
- "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must
- # exist the `Release` to be created.
- "createTime": "A String", # Time the release was created.
- # Output only.
- "updateTime": "A String", # Time the release was updated.
- # Output only.
-}
+{ # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
+ "name": "A String", # Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`
+ "createTime": "A String", # Time the release was created. Output only.
+ "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must exist the `Release` to be created.
+ "updateTime": "A String", # Time the release was updated. Output only.
+ }
x__xgafv: string, V1 error format.
Allowed values
@@ -170,39 +128,12 @@
Returns:
An object of the form:
- { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a
- # `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
- "name": "A String", # Resource name for the `Release`.
- #
- # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
- # which affords developers a great deal of flexibility in mapping the name
- # to the style that best fits their existing development practices. For
- # example, a name could refer to an environment, an app, a version, or some
- # combination of three.
- #
- # In the table below, for the project name `projects/foo`, the following
- # relative release paths show how flat and structured names might be chosen
- # to match a desired development / deployment strategy.
- #
- # Use Case | Flat Name | Structured Name
- # -------------|---------------------|----------------
- # Environments | releases/qa | releases/qa
- # Apps | releases/app1_qa | releases/app1/qa
- # Versions | releases/app1_v2_qa | releases/app1/v2/qa
- #
- # The delimiter between the release name path elements can be almost anything
- # and it should work equally well with the release name list filter, but in
- # many ways the structured paths provide a clearer picture of the
- # relationship between `Release` instances.
- #
- # Format: `projects/{project_id}/releases/{release_id}`
- "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must
- # exist the `Release` to be created.
- "createTime": "A String", # Time the release was created.
- # Output only.
- "updateTime": "A String", # Time the release was updated.
- # Output only.
- }</pre>
+ { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
+ "name": "A String", # Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`
+ "createTime": "A String", # Time the release was created. Output only.
+ "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must exist the `Release` to be created.
+ "updateTime": "A String", # Time the release was updated. Output only.
+ }</pre>
</div>
<div class="method">
@@ -210,9 +141,7 @@
<pre>Delete a `Release` by resource name.
Args:
- name: string, Resource name for the `Release` to delete.
-
-Format: `projects/{project_id}/releases/{release_id}` (required)
+ name: string, Resource name for the `Release` to delete. Format: `projects/{project_id}/releases/{release_id}` (required)
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -221,15 +150,7 @@
Returns:
An object of the form:
- { # A generic empty message that you can re-use to avoid defining duplicated
- # empty messages in your APIs. A typical example is to use it as the request
- # or the response type of an API method. For instance:
- #
- # service Foo {
- # rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
- # }
- #
- # The JSON representation for `Empty` is empty JSON object `{}`.
+ { # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
}</pre>
</div>
@@ -238,9 +159,7 @@
<pre>Get a `Release` by name.
Args:
- name: string, Resource name of the `Release`.
-
-Format: `projects/{project_id}/releases/{release_id}` (required)
+ name: string, Resource name of the `Release`. Format: `projects/{project_id}/releases/{release_id}` (required)
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -249,39 +168,12 @@
Returns:
An object of the form:
- { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a
- # `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
- "name": "A String", # Resource name for the `Release`.
- #
- # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
- # which affords developers a great deal of flexibility in mapping the name
- # to the style that best fits their existing development practices. For
- # example, a name could refer to an environment, an app, a version, or some
- # combination of three.
- #
- # In the table below, for the project name `projects/foo`, the following
- # relative release paths show how flat and structured names might be chosen
- # to match a desired development / deployment strategy.
- #
- # Use Case | Flat Name | Structured Name
- # -------------|---------------------|----------------
- # Environments | releases/qa | releases/qa
- # Apps | releases/app1_qa | releases/app1/qa
- # Versions | releases/app1_v2_qa | releases/app1/v2/qa
- #
- # The delimiter between the release name path elements can be almost anything
- # and it should work equally well with the release name list filter, but in
- # many ways the structured paths provide a clearer picture of the
- # relationship between `Release` instances.
- #
- # Format: `projects/{project_id}/releases/{release_id}`
- "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must
- # exist the `Release` to be created.
- "createTime": "A String", # Time the release was created.
- # Output only.
- "updateTime": "A String", # Time the release was updated.
- # Output only.
- }</pre>
+ { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
+ "name": "A String", # Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`
+ "createTime": "A String", # Time the release was created. Output only.
+ "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must exist the `Release` to be created.
+ "updateTime": "A String", # Time the release was updated. Output only.
+ }</pre>
</div>
<div class="method">
@@ -289,11 +181,12 @@
<pre>Get the `Release` executable to use when enforcing rules.
Args:
- name: string, Resource name of the `Release`.
-
-Format: `projects/{project_id}/releases/{release_id}` (required)
- executableVersion: string, The requested runtime executable version.
-Defaults to FIREBASE_RULES_EXECUTABLE_V1.
+ name: string, Resource name of the `Release`. Format: `projects/{project_id}/releases/{release_id}` (required)
+ executableVersion: string, The requested runtime executable version. Defaults to FIREBASE_RULES_EXECUTABLE_V1.
+ Allowed values
+ RELEASE_EXECUTABLE_VERSION_UNSPECIFIED - Executable format unspecified. Defaults to FIREBASE_RULES_EXECUTABLE_V1
+ FIREBASE_RULES_EXECUTABLE_V1 - Firebase Rules syntax 'rules2' executable versions: Custom AST for use with Java clients.
+ FIREBASE_RULES_EXECUTABLE_V2 - CEL-based executable for use with C++ clients.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -304,56 +197,23 @@
{ # The response for FirebaseRulesService.GetReleaseExecutable
"executableVersion": "A String", # The Rules runtime version of the executable.
- "updateTime": "A String", # Timestamp for the most recent `Release.update_time`.
"executable": "A String", # Executable view of the `Ruleset` referenced by the `Release`.
+ "updateTime": "A String", # Timestamp for the most recent `Release.update_time`.
"rulesetName": "A String", # `Ruleset` name associated with the `Release` executable.
- "syncTime": "A String", # Optional, indicates the freshness of the result. The response is
- # guaranteed to be the latest within an interval up to the
- # sync_time (inclusive).
+ "syncTime": "A String", # Optional, indicates the freshness of the result. The response is guaranteed to be the latest within an interval up to the sync_time (inclusive).
"language": "A String", # `Language` used to generate the executable bytes.
}</pre>
</div>
<div class="method">
- <code class="details" id="list">list(name, filter=None, pageSize=None, pageToken=None, x__xgafv=None)</code>
- <pre>List the `Release` values for a project. This list may optionally be
-filtered by `Release` name, `Ruleset` name, `TestSuite` name, or any
-combination thereof.
+ <code class="details" id="list">list(name, pageToken=None, pageSize=None, filter=None, x__xgafv=None)</code>
+ <pre>List the `Release` values for a project. This list may optionally be filtered by `Release` name, `Ruleset` name, `TestSuite` name, or any combination thereof.
Args:
- name: string, Resource name for the project.
-
-Format: `projects/{project_id}` (required)
- filter: string, `Release` filter. The list method supports filters with restrictions on the
-`Release.name`, `Release.ruleset_name`, and `Release.test_suite_name`.
-
-Example 1: A filter of 'name=prod*' might return `Release`s with names
-within 'projects/foo' prefixed with 'prod':
-
-Name | Ruleset Name
-------------------------------|-------------
-projects/foo/releases/prod | projects/foo/rulesets/uuid1234
-projects/foo/releases/prod/v1 | projects/foo/rulesets/uuid1234
-projects/foo/releases/prod/v2 | projects/foo/rulesets/uuid8888
-
-Example 2: A filter of `name=prod* ruleset_name=uuid1234` would return only
-`Release` instances for 'projects/foo' with names prefixed with 'prod'
-referring to the same `Ruleset` name of 'uuid1234':
-
-Name | Ruleset Name
-------------------------------|-------------
-projects/foo/releases/prod | projects/foo/rulesets/1234
-projects/foo/releases/prod/v1 | projects/foo/rulesets/1234
-
-In the examples, the filter parameters refer to the search filters are
-relative to the project. Fully qualified prefixed may also be used. e.g.
-`test_suite_name=projects/foo/testsuites/uuid1`
- pageSize: integer, Page size to load. Maximum of 100. Defaults to 10.
-Note: `page_size` is just a hint and the service may choose to load fewer
-than `page_size` results due to the size of the output. To traverse all of
-the releases, the caller should iterate until the `page_token` on the
-response is empty.
+ name: string, Resource name for the project. Format: `projects/{project_id}` (required)
pageToken: string, Next page token for the next batch of `Release` instances.
+ pageSize: integer, Page size to load. Maximum of 100. Defaults to 10. Note: `page_size` is just a hint and the service may choose to load fewer than `page_size` results due to the size of the output. To traverse all of the releases, the caller should iterate until the `page_token` on the response is empty.
+ filter: string, `Release` filter. The list method supports filters with restrictions on the `Release.name`, `Release.ruleset_name`, and `Release.test_suite_name`. Example 1: A filter of 'name=prod*' might return `Release`s with names within 'projects/foo' prefixed with 'prod': Name | Ruleset Name ------------------------------|------------- projects/foo/releases/prod | projects/foo/rulesets/uuid1234 projects/foo/releases/prod/v1 | projects/foo/rulesets/uuid1234 projects/foo/releases/prod/v2 | projects/foo/rulesets/uuid8888 Example 2: A filter of `name=prod* ruleset_name=uuid1234` would return only `Release` instances for 'projects/foo' with names prefixed with 'prod' referring to the same `Ruleset` name of 'uuid1234': Name | Ruleset Name ------------------------------|------------- projects/foo/releases/prod | projects/foo/rulesets/1234 projects/foo/releases/prod/v1 | projects/foo/rulesets/1234 In the examples, the filter parameters refer to the search filters are relative to the project. Fully qualified prefixed may also be used. e.g. `test_suite_name=projects/foo/testsuites/uuid1`
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -363,43 +223,15 @@
An object of the form:
{ # The response for FirebaseRulesService.ListReleases.
+ "nextPageToken": "A String", # The pagination token to retrieve the next page of results. If the value is empty, no further results remain.
"releases": [ # List of `Release` instances.
- { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a
- # `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
- "name": "A String", # Resource name for the `Release`.
- #
- # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
- # which affords developers a great deal of flexibility in mapping the name
- # to the style that best fits their existing development practices. For
- # example, a name could refer to an environment, an app, a version, or some
- # combination of three.
- #
- # In the table below, for the project name `projects/foo`, the following
- # relative release paths show how flat and structured names might be chosen
- # to match a desired development / deployment strategy.
- #
- # Use Case | Flat Name | Structured Name
- # -------------|---------------------|----------------
- # Environments | releases/qa | releases/qa
- # Apps | releases/app1_qa | releases/app1/qa
- # Versions | releases/app1_v2_qa | releases/app1/v2/qa
- #
- # The delimiter between the release name path elements can be almost anything
- # and it should work equally well with the release name list filter, but in
- # many ways the structured paths provide a clearer picture of the
- # relationship between `Release` instances.
- #
- # Format: `projects/{project_id}/releases/{release_id}`
- "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must
- # exist the `Release` to be created.
- "createTime": "A String", # Time the release was created.
- # Output only.
- "updateTime": "A String", # Time the release was updated.
- # Output only.
- },
+ { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
+ "name": "A String", # Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`
+ "createTime": "A String", # Time the release was created. Output only.
+ "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must exist the `Release` to be created.
+ "updateTime": "A String", # Time the release was updated. Output only.
+ },
],
- "nextPageToken": "A String", # The pagination token to retrieve the next page of results. If the value is
- # empty, no further results remain.
}</pre>
</div>
@@ -419,54 +251,21 @@
<div class="method">
<code class="details" id="patch">patch(name, body=None, x__xgafv=None)</code>
- <pre>Update a `Release` via PATCH.
-
-Only updates to the `ruleset_name` and `test_suite_name` fields will be
-honored. `Release` rename is not supported. To create a `Release` use the
-CreateRelease method.
+ <pre>Update a `Release` via PATCH. Only updates to the `ruleset_name` and `test_suite_name` fields will be honored. `Release` rename is not supported. To create a `Release` use the CreateRelease method.
Args:
- name: string, Resource name for the project which owns this `Release`.
-
-Format: `projects/{project_id}` (required)
+ name: string, Resource name for the project which owns this `Release`. Format: `projects/{project_id}` (required)
body: object, The request body.
The object takes the form of:
{ # The request for FirebaseRulesService.UpdateReleasePatch.
"updateMask": "A String", # Specifies which fields to update.
- "release": { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a # `Release` to update.
- # `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
- "name": "A String", # Resource name for the `Release`.
- #
- # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
- # which affords developers a great deal of flexibility in mapping the name
- # to the style that best fits their existing development practices. For
- # example, a name could refer to an environment, an app, a version, or some
- # combination of three.
- #
- # In the table below, for the project name `projects/foo`, the following
- # relative release paths show how flat and structured names might be chosen
- # to match a desired development / deployment strategy.
- #
- # Use Case | Flat Name | Structured Name
- # -------------|---------------------|----------------
- # Environments | releases/qa | releases/qa
- # Apps | releases/app1_qa | releases/app1/qa
- # Versions | releases/app1_v2_qa | releases/app1/v2/qa
- #
- # The delimiter between the release name path elements can be almost anything
- # and it should work equally well with the release name list filter, but in
- # many ways the structured paths provide a clearer picture of the
- # relationship between `Release` instances.
- #
- # Format: `projects/{project_id}/releases/{release_id}`
- "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must
- # exist the `Release` to be created.
- "createTime": "A String", # Time the release was created.
- # Output only.
- "updateTime": "A String", # Time the release was updated.
- # Output only.
- },
+ "release": { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`. # `Release` to update.
+ "name": "A String", # Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`
+ "createTime": "A String", # Time the release was created. Output only.
+ "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must exist the `Release` to be created.
+ "updateTime": "A String", # Time the release was updated. Output only.
+ },
}
x__xgafv: string, V1 error format.
@@ -477,39 +276,12 @@
Returns:
An object of the form:
- { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a
- # `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
- "name": "A String", # Resource name for the `Release`.
- #
- # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
- # which affords developers a great deal of flexibility in mapping the name
- # to the style that best fits their existing development practices. For
- # example, a name could refer to an environment, an app, a version, or some
- # combination of three.
- #
- # In the table below, for the project name `projects/foo`, the following
- # relative release paths show how flat and structured names might be chosen
- # to match a desired development / deployment strategy.
- #
- # Use Case | Flat Name | Structured Name
- # -------------|---------------------|----------------
- # Environments | releases/qa | releases/qa
- # Apps | releases/app1_qa | releases/app1/qa
- # Versions | releases/app1_v2_qa | releases/app1/v2/qa
- #
- # The delimiter between the release name path elements can be almost anything
- # and it should work equally well with the release name list filter, but in
- # many ways the structured paths provide a clearer picture of the
- # relationship between `Release` instances.
- #
- # Format: `projects/{project_id}/releases/{release_id}`
- "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must
- # exist the `Release` to be created.
- "createTime": "A String", # Time the release was created.
- # Output only.
- "updateTime": "A String", # Time the release was updated.
- # Output only.
- }</pre>
+ { # `Release` is a named reference to a `Ruleset`. Once a `Release` refers to a `Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.
+ "name": "A String", # Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`
+ "createTime": "A String", # Time the release was created. Output only.
+ "rulesetName": "A String", # Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must exist the `Release` to be created.
+ "updateTime": "A String", # Time the release was updated. Output only.
+ }</pre>
</div>
</body></html>
\ No newline at end of file