chore: regens API reference docs (#889)
diff --git a/docs/dyn/servicemanagement_v1.services.rollouts.html b/docs/dyn/servicemanagement_v1.services.rollouts.html
index 935668b..2c8b774 100644
--- a/docs/dyn/servicemanagement_v1.services.rollouts.html
+++ b/docs/dyn/servicemanagement_v1.services.rollouts.html
@@ -75,7 +75,7 @@
<h1><a href="servicemanagement_v1.html">Service Management API</a> . <a href="servicemanagement_v1.services.html">services</a> . <a href="servicemanagement_v1.services.rollouts.html">rollouts</a></h1>
<h2>Instance Methods</h2>
<p class="toc_element">
- <code><a href="#create">create(serviceName, body, baseRolloutId=None, x__xgafv=None)</a></code></p>
+ <code><a href="#create">create(serviceName, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Creates a new service configuration rollout. Based on rollout, the</p>
<p class="toc_element">
<code><a href="#get">get(serviceName, rolloutId, x__xgafv=None)</a></code></p>
@@ -88,7 +88,7 @@
<p class="firstline">Retrieves the next page of results.</p>
<h3>Method Details</h3>
<div class="method">
- <code class="details" id="create">create(serviceName, body, baseRolloutId=None, x__xgafv=None)</code>
+ <code class="details" id="create">create(serviceName, body=None, x__xgafv=None)</code>
<pre>Creates a new service configuration rollout. Based on rollout, the
Google Service Management will roll out the service configurations to
different backend services. For example, the logging configuration will be
@@ -102,12 +102,12 @@
already part of the set of 100 most recent) rollouts are kept for each
service. The rest will be deleted eventually.
-Operation<response: Rollout>
+Operation<response: Rollout>
Args:
- serviceName: string, The name of the service. See the [overview](/service-management/overview)
+ serviceName: string, Required. The name of the service. See the [overview](/service-management/overview)
for naming requirements. For example: `example.googleapis.com`. (required)
- body: object, The request body. (required)
+ body: object, The request body.
The object takes the form of:
{ # A rollout resource that defines how service configuration versions are pushed
@@ -119,7 +119,7 @@
"trafficPercentStrategy": { # Strategy that specifies how clients of Google Service Controller want to # Google Service Control selects service configurations based on
# traffic percentage.
# send traffic to use different config versions. This is generally
- # used by API proxy to split traffic based on your configured precentage for
+ # used by API proxy to split traffic based on your configured percentage for
# each config version.
#
# One example of how to gradually rollout a new service configuration using
@@ -153,16 +153,17 @@
"a_key": 3.14,
},
},
- "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
- # and '-' are allowed.
+ "rolloutId": "A String", # Optional. Unique identifier of this Rollout. Must be no longer than 63 characters
+ # and only lower case letters, digits, '.', '_' and '-' are allowed.
#
# If not specified by client, the server will generate one. The generated id
- # will have the form of <date><revision number>, where "date" is the create
+ # will have the form of <date><revision number>, where "date" is the create
# date in ISO 8601 format. "revision number" is a monotonically increasing
# positive number that is reset every day for each service.
# An example of the generated rollout_id is '2016-02-16r1'
"serviceName": "A String", # The name of the service associated with this Rollout.
- "createdBy": "A String", # The user who created the Rollout. Readonly.
+ "createdBy": "A String", # This field is deprecated and will be deleted. Please remove usage of
+ # this field.
"deleteServiceStrategy": { # Strategy used to delete a service. This strategy is a placeholder only # The strategy associated with a rollout to delete a `ManagedService`.
# Readonly.
# used by the system generated rollout to delete a service.
@@ -170,14 +171,6 @@
"createTime": "A String", # Creation time of the rollout. Readonly.
}
- baseRolloutId: string, Unimplemented. Do not use this feature until this comment is removed.
-
-The rollout id that rollout to be created based on.
-
-Rollout should be constructed based on current successful rollout, this
-field indicates the current successful rollout id that new rollout based on
-to construct, if current successful rollout changed when server receives
-the request, request will be rejected for safety.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -188,28 +181,12 @@
{ # This resource represents a long-running operation that is the result of a
# network API call.
- "response": { # The normal response of the operation in case of success. If the original
- # method returns no data on success, such as `Delete`, the response is
- # `google.protobuf.Empty`. If the original method is standard
- # `Get`/`Create`/`Update`, the response should be the resource. For other
- # methods, the response should have the type `XxxResponse`, where `Xxx`
- # is the original method name. For example, if the original method name
- # is `TakeSnapshot()`, the inferred response type is
- # `TakeSnapshotResponse`.
- "a_key": "", # Properties of the object. Contains field @type with type URL.
- },
"metadata": { # Service-specific metadata associated with the operation. It typically
# contains progress information and common metadata such as create time.
# Some services might not provide such metadata. Any method that returns a
# long-running operation should document the metadata type, if any.
"a_key": "", # Properties of the object. Contains field @type with type URL.
},
- "done": True or False, # If the value is `false`, it means the operation is still in progress.
- # If `true`, the operation is completed, and either `error` or `response` is
- # available.
- "name": "A String", # The server-assigned name, which is only unique within the same service that
- # originally returns it. If you use the default HTTP mapping, the
- # `name` should be a resource name ending with `operations/{unique_id}`.
"error": { # The `Status` type defines a logical error model that is suitable for # The error result of the operation in case of failure or cancellation.
# different programming environments, including REST APIs and RPC APIs. It is
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
@@ -228,6 +205,22 @@
},
],
},
+ "done": True or False, # If the value is `false`, it means the operation is still in progress.
+ # If `true`, the operation is completed, and either `error` or `response` is
+ # available.
+ "response": { # The normal response of the operation in case of success. If the original
+ # method returns no data on success, such as `Delete`, the response is
+ # `google.protobuf.Empty`. If the original method is standard
+ # `Get`/`Create`/`Update`, the response should be the resource. For other
+ # methods, the response should have the type `XxxResponse`, where `Xxx`
+ # is the original method name. For example, if the original method name
+ # is `TakeSnapshot()`, the inferred response type is
+ # `TakeSnapshotResponse`.
+ "a_key": "", # Properties of the object. Contains field @type with type URL.
+ },
+ "name": "A String", # The server-assigned name, which is only unique within the same service that
+ # originally returns it. If you use the default HTTP mapping, the
+ # `name` should be a resource name ending with `operations/{unique_id}`.
}</pre>
</div>
@@ -236,9 +229,9 @@
<pre>Gets a service configuration rollout.
Args:
- serviceName: string, The name of the service. See the [overview](/service-management/overview)
+ serviceName: string, Required. The name of the service. See the [overview](/service-management/overview)
for naming requirements. For example: `example.googleapis.com`. (required)
- rolloutId: string, The id of the rollout resource. (required)
+ rolloutId: string, Required. The id of the rollout resource. (required)
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -256,7 +249,7 @@
"trafficPercentStrategy": { # Strategy that specifies how clients of Google Service Controller want to # Google Service Control selects service configurations based on
# traffic percentage.
# send traffic to use different config versions. This is generally
- # used by API proxy to split traffic based on your configured precentage for
+ # used by API proxy to split traffic based on your configured percentage for
# each config version.
#
# One example of how to gradually rollout a new service configuration using
@@ -290,16 +283,17 @@
"a_key": 3.14,
},
},
- "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
- # and '-' are allowed.
+ "rolloutId": "A String", # Optional. Unique identifier of this Rollout. Must be no longer than 63 characters
+ # and only lower case letters, digits, '.', '_' and '-' are allowed.
#
# If not specified by client, the server will generate one. The generated id
- # will have the form of <date><revision number>, where "date" is the create
+ # will have the form of <date><revision number>, where "date" is the create
# date in ISO 8601 format. "revision number" is a monotonically increasing
# positive number that is reset every day for each service.
# An example of the generated rollout_id is '2016-02-16r1'
"serviceName": "A String", # The name of the service associated with this Rollout.
- "createdBy": "A String", # The user who created the Rollout. Readonly.
+ "createdBy": "A String", # This field is deprecated and will be deleted. Please remove usage of
+ # this field.
"deleteServiceStrategy": { # Strategy used to delete a service. This strategy is a placeholder only # The strategy associated with a rollout to delete a `ManagedService`.
# Readonly.
# used by the system generated rollout to delete a service.
@@ -314,7 +308,7 @@
service, from the newest to the oldest.
Args:
- serviceName: string, The name of the service. See the [overview](/service-management/overview)
+ serviceName: string, Required. The name of the service. See the [overview](/service-management/overview)
for naming requirements. For example: `example.googleapis.com`. (required)
pageSize: integer, The max number of items to include in the response list. Page size is 50
if not specified. Maximum value is 100.
@@ -323,7 +317,7 @@
Allowed values
1 - v1 error format
2 - v2 error format
- filter: string, Use `filter` to return subset of rollouts.
+ filter: string, Required. Use `filter` to return subset of rollouts.
The following filters are supported:
-- To limit the results to only those in
[status](google.api.servicemanagement.v1.RolloutStatus) 'SUCCESS',
@@ -347,7 +341,7 @@
"trafficPercentStrategy": { # Strategy that specifies how clients of Google Service Controller want to # Google Service Control selects service configurations based on
# traffic percentage.
# send traffic to use different config versions. This is generally
- # used by API proxy to split traffic based on your configured precentage for
+ # used by API proxy to split traffic based on your configured percentage for
# each config version.
#
# One example of how to gradually rollout a new service configuration using
@@ -381,16 +375,17 @@
"a_key": 3.14,
},
},
- "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
- # and '-' are allowed.
+ "rolloutId": "A String", # Optional. Unique identifier of this Rollout. Must be no longer than 63 characters
+ # and only lower case letters, digits, '.', '_' and '-' are allowed.
#
# If not specified by client, the server will generate one. The generated id
- # will have the form of <date><revision number>, where "date" is the create
+ # will have the form of <date><revision number>, where "date" is the create
# date in ISO 8601 format. "revision number" is a monotonically increasing
# positive number that is reset every day for each service.
# An example of the generated rollout_id is '2016-02-16r1'
"serviceName": "A String", # The name of the service associated with this Rollout.
- "createdBy": "A String", # The user who created the Rollout. Readonly.
+ "createdBy": "A String", # This field is deprecated and will be deleted. Please remove usage of
+ # this field.
"deleteServiceStrategy": { # Strategy used to delete a service. This strategy is a placeholder only # The strategy associated with a rollout to delete a `ManagedService`.
# Readonly.
# used by the system generated rollout to delete a service.