Skip to content

Commit

Permalink
feat(serviceusage): update the api
Browse files Browse the repository at this point in the history
#### serviceusage:v1

The following keys were added:
- schemas.ExperimentalFeatures.properties.protobufPythonicTypesEnabled.type (Total Keys: 1)
- schemas.GoSettings.properties.renamedServices (Total Keys: 2)

#### serviceusage:v1beta1

The following keys were added:
- schemas.ExperimentalFeatures.properties.protobufPythonicTypesEnabled.type (Total Keys: 1)
- schemas.GoSettings.properties.renamedServices (Total Keys: 2)
  • Loading branch information
yoshi-automation committed Nov 26, 2024
1 parent 2a30279 commit 0a24948
Show file tree
Hide file tree
Showing 5 changed files with 34 additions and 12 deletions.
4 changes: 2 additions & 2 deletions docs/dyn/serviceusage_v1.operations.html
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ <h1><a href="serviceusage_v1.html">Service Usage API</a> . <a href="serviceusage
<h2>Instance Methods</h2>
<p class="toc_element">
<code><a href="#cancel">cancel(name, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.</p>
<p class="firstline">Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.</p>
<p class="toc_element">
<code><a href="#close">close()</a></code></p>
<p class="firstline">Close httplib2 connections.</p>
Expand All @@ -95,7 +95,7 @@ <h2>Instance Methods</h2>
<h3>Method Details</h3>
<div class="method">
<code class="details" id="cancel">cancel(name, body=None, x__xgafv=None)</code>
<pre>Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn&#x27;t support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.
<pre>Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn&#x27;t support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.

Args:
name: string, The name of the operation resource to be cancelled. (required)
Expand Down
6 changes: 3 additions & 3 deletions docs/dyn/serviceusage_v1.services.html
Original file line number Diff line number Diff line change
Expand Up @@ -326,7 +326,7 @@ <h3>Method Details</h3>
&quot;maxLimit&quot;: &quot;A String&quot;, # Maximum number of tokens that can be consumed during the specified duration. Client application developers can override the default limit up to this maximum. If specified, this value cannot be set to a value less than the default limit. If not specified, it is set to the default limit. To allow clients to apply overrides with no upper bound, set this to -1, indicating unlimited maximum quota. Used by group-based quotas only.
&quot;metric&quot;: &quot;A String&quot;, # The name of the metric this quota limit applies to. The quota limits with the same metric will be checked together during runtime. The metric must be defined within the service config.
&quot;name&quot;: &quot;A String&quot;, # Name of the quota limit. The name must be provided, and it must be unique within the service. The name can only include alphanumeric characters as well as &#x27;-&#x27;. The maximum length of the limit name is 64 characters.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;values&quot;: { # Tiered limit values. You must specify this as a key:value pair, with an integer value that is the maximum number of requests allowed for the specified unit. Currently only STANDARD is supported.
&quot;a_key&quot;: &quot;A String&quot;,
},
Expand Down Expand Up @@ -633,7 +633,7 @@ <h3>Method Details</h3>
&quot;maxLimit&quot;: &quot;A String&quot;, # Maximum number of tokens that can be consumed during the specified duration. Client application developers can override the default limit up to this maximum. If specified, this value cannot be set to a value less than the default limit. If not specified, it is set to the default limit. To allow clients to apply overrides with no upper bound, set this to -1, indicating unlimited maximum quota. Used by group-based quotas only.
&quot;metric&quot;: &quot;A String&quot;, # The name of the metric this quota limit applies to. The quota limits with the same metric will be checked together during runtime. The metric must be defined within the service config.
&quot;name&quot;: &quot;A String&quot;, # Name of the quota limit. The name must be provided, and it must be unique within the service. The name can only include alphanumeric characters as well as &#x27;-&#x27;. The maximum length of the limit name is 64 characters.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;values&quot;: { # Tiered limit values. You must specify this as a key:value pair, with an integer value that is the maximum number of requests allowed for the specified unit. Currently only STANDARD is supported.
&quot;a_key&quot;: &quot;A String&quot;,
},
Expand Down Expand Up @@ -855,7 +855,7 @@ <h3>Method Details</h3>
&quot;maxLimit&quot;: &quot;A String&quot;, # Maximum number of tokens that can be consumed during the specified duration. Client application developers can override the default limit up to this maximum. If specified, this value cannot be set to a value less than the default limit. If not specified, it is set to the default limit. To allow clients to apply overrides with no upper bound, set this to -1, indicating unlimited maximum quota. Used by group-based quotas only.
&quot;metric&quot;: &quot;A String&quot;, # The name of the metric this quota limit applies to. The quota limits with the same metric will be checked together during runtime. The metric must be defined within the service config.
&quot;name&quot;: &quot;A String&quot;, # Name of the quota limit. The name must be provided, and it must be unique within the service. The name can only include alphanumeric characters as well as &#x27;-&#x27;. The maximum length of the limit name is 64 characters.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;values&quot;: { # Tiered limit values. You must specify this as a key:value pair, with an integer value that is the maximum number of requests allowed for the specified unit. Currently only STANDARD is supported.
&quot;a_key&quot;: &quot;A String&quot;,
},
Expand Down
4 changes: 2 additions & 2 deletions docs/dyn/serviceusage_v1beta1.services.html
Original file line number Diff line number Diff line change
Expand Up @@ -450,7 +450,7 @@ <h3>Method Details</h3>
&quot;maxLimit&quot;: &quot;A String&quot;, # Maximum number of tokens that can be consumed during the specified duration. Client application developers can override the default limit up to this maximum. If specified, this value cannot be set to a value less than the default limit. If not specified, it is set to the default limit. To allow clients to apply overrides with no upper bound, set this to -1, indicating unlimited maximum quota. Used by group-based quotas only.
&quot;metric&quot;: &quot;A String&quot;, # The name of the metric this quota limit applies to. The quota limits with the same metric will be checked together during runtime. The metric must be defined within the service config.
&quot;name&quot;: &quot;A String&quot;, # Name of the quota limit. The name must be provided, and it must be unique within the service. The name can only include alphanumeric characters as well as &#x27;-&#x27;. The maximum length of the limit name is 64 characters.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;values&quot;: { # Tiered limit values. You must specify this as a key:value pair, with an integer value that is the maximum number of requests allowed for the specified unit. Currently only STANDARD is supported.
&quot;a_key&quot;: &quot;A String&quot;,
},
Expand Down Expand Up @@ -672,7 +672,7 @@ <h3>Method Details</h3>
&quot;maxLimit&quot;: &quot;A String&quot;, # Maximum number of tokens that can be consumed during the specified duration. Client application developers can override the default limit up to this maximum. If specified, this value cannot be set to a value less than the default limit. If not specified, it is set to the default limit. To allow clients to apply overrides with no upper bound, set this to -1, indicating unlimited maximum quota. Used by group-based quotas only.
&quot;metric&quot;: &quot;A String&quot;, # The name of the metric this quota limit applies to. The quota limits with the same metric will be checked together during runtime. The metric must be defined within the service config.
&quot;name&quot;: &quot;A String&quot;, # Name of the quota limit. The name must be provided, and it must be unique within the service. The name can only include alphanumeric characters as well as &#x27;-&#x27;. The maximum length of the limit name is 64 characters.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;unit&quot;: &quot;A String&quot;, # Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * &quot;1/min/{project}&quot; for quota per minute per project. Note: the order of unit components is insignificant. The &quot;1&quot; at the beginning is required to follow the metric unit syntax.
&quot;values&quot;: { # Tiered limit values. You must specify this as a key:value pair, with an integer value that is the maximum number of requests allowed for the specified unit. Currently only STANDARD is supported.
&quot;a_key&quot;: &quot;A String&quot;,
},
Expand Down
17 changes: 14 additions & 3 deletions googleapiclient/discovery_cache/documents/serviceusage.v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@
"operations": {
"methods": {
"cancel": {
"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.",
"flatPath": "v1/operations/{operationsId}:cancel",
"httpMethod": "POST",
"id": "serviceusage.operations.cancel",
Expand Down Expand Up @@ -426,7 +426,7 @@
}
}
},
"revision": "20241025",
"revision": "20241115",
"rootUrl": "https://serviceusage.googleapis.com/",
"schemas": {
"AddEnableRulesMetadata": {
Expand Down Expand Up @@ -1524,6 +1524,10 @@
"description": "Experimental features to be included during client library generation. These fields will be deprecated once the feature graduates and is enabled by default.",
"id": "ExperimentalFeatures",
"properties": {
"protobufPythonicTypesEnabled": {
"description": "Enables generation of protobuf code using new types that are more Pythonic which are included in `protobuf>=5.29.x`. This feature will be enabled by default 1 month after launching the feature in preview packages.",
"type": "boolean"
},
"restAsyncIoEnabled": {
"description": "Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages.",
"type": "boolean"
Expand Down Expand Up @@ -1692,6 +1696,13 @@
"common": {
"$ref": "CommonLanguageSettings",
"description": "Some settings."
},
"renamedServices": {
"additionalProperties": {
"type": "string"
},
"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
"type": "object"
}
},
"type": "object"
Expand Down Expand Up @@ -3226,7 +3237,7 @@
"type": "string"
},
"unit": {
"description": "Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
"description": "Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
"type": "string"
},
"values": {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -964,7 +964,7 @@
}
}
},
"revision": "20241025",
"revision": "20241115",
"rootUrl": "https://serviceusage.googleapis.com/",
"schemas": {
"AddEnableRulesMetadata": {
Expand Down Expand Up @@ -2101,6 +2101,10 @@
"description": "Experimental features to be included during client library generation. These fields will be deprecated once the feature graduates and is enabled by default.",
"id": "ExperimentalFeatures",
"properties": {
"protobufPythonicTypesEnabled": {
"description": "Enables generation of protobuf code using new types that are more Pythonic which are included in `protobuf>=5.29.x`. This feature will be enabled by default 1 month after launching the feature in preview packages.",
"type": "boolean"
},
"restAsyncIoEnabled": {
"description": "Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages.",
"type": "boolean"
Expand Down Expand Up @@ -2269,6 +2273,13 @@
"common": {
"$ref": "CommonLanguageSettings",
"description": "Some settings."
},
"renamedServices": {
"additionalProperties": {
"type": "string"
},
"description": "Map of service names to renamed services. Keys are the package relative service names and values are the name to be used for the service client and call options. publishing: go_settings: renamed_services: Publisher: TopicAdmin",
"type": "object"
}
},
"type": "object"
Expand Down Expand Up @@ -4014,7 +4025,7 @@
"type": "string"
},
"unit": {
"description": "Specify the unit of the quota limit. It uses the same syntax as Metric.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
"description": "Specify the unit of the quota limit. It uses the same syntax as MetricDescriptor.unit. The supported unit kinds are determined by the quota backend system. Here are some examples: * \"1/min/{project}\" for quota per minute per project. Note: the order of unit components is insignificant. The \"1\" at the beginning is required to follow the metric unit syntax.",
"type": "string"
},
"values": {
Expand Down

0 comments on commit 0a24948

Please sign in to comment.