Skip to content

Commit

Permalink
feat(all): auto-regenerate discovery clients (#2229)
Browse files Browse the repository at this point in the history
  • Loading branch information
yoshi-automation committed Oct 20, 2023
1 parent 5e4c19e commit 199783c
Show file tree
Hide file tree
Showing 14 changed files with 68 additions and 22 deletions.
4 changes: 2 additions & 2 deletions analyticsadmin/v1alpha/analyticsadmin-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -4298,7 +4298,7 @@
}
}
},
"revision": "20231004",
"revision": "20231018",
"rootUrl": "https://analyticsadmin.googleapis.com/",
"schemas": {
"GoogleAnalyticsAdminV1alphaAccessBetweenFilter": {
Expand Down Expand Up @@ -5668,7 +5668,7 @@
"type": "string"
},
"systemDefined": {
"description": "Output only. Default Channel Group defined by Google, which cannot be updated.",
"description": "Output only. If true, then this channel group is the Default Channel Group predefined by Google Analytics. Display name and grouping rules cannot be updated for this channel group.",
"readOnly": true,
"type": "boolean"
}
Expand Down
5 changes: 3 additions & 2 deletions analyticsadmin/v1alpha/analyticsadmin-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 3 additions & 3 deletions androidenterprise/v1/androidenterprise-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -2649,7 +2649,7 @@
}
}
},
"revision": "20230801",
"revision": "20231018",
"rootUrl": "https://androidenterprise.googleapis.com/",
"schemas": {
"Administrator": {
Expand Down Expand Up @@ -3990,11 +3990,11 @@
"id": "Permission",
"properties": {
"description": {
"description": "A longer description of the Permissions resource, giving more details of what it affects.",
"description": "A longer description of the Permissions resource, giving more details of what it affects. This field may be absent.",
"type": "string"
},
"name": {
"description": "The name of the permission.",
"description": "The name of the permission. This field may be absent.",
"type": "string"
},
"permissionId": {
Expand Down
4 changes: 2 additions & 2 deletions androidenterprise/v1/androidenterprise-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 6 additions & 1 deletion assuredworkloads/v1/assuredworkloads-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -566,7 +566,7 @@
}
}
},
"revision": "20230914",
"revision": "20231017",
"rootUrl": "https://assuredworkloads.googleapis.com/",
"schemas": {
"GoogleCloudAssuredworkloadsV1AcknowledgeViolationRequest": {
Expand Down Expand Up @@ -1207,6 +1207,11 @@
"description": "Input only. The parent resource for the resources managed by this Assured Workload. May be either empty or a folder resource which is a child of the Workload parent. If not specified all resources are created under the parent organization. Format: folders/{folder_id}",
"type": "string"
},
"resourceMonitoringEnabled": {
"description": "Output only. Indicates whether resource monitoring is enabled for workload or not. It is true when Resource feed is subscribed to AWM topic and AWM Service Agent Role is binded to AW Service Account for resource Assured workload.",
"readOnly": true,
"type": "boolean"
},
"resourceSettings": {
"description": "Input only. Resource properties that are used to customize workload resources. These properties (such as custom project id) will be used to create workload resources if possible. This field is optional.",
"items": {
Expand Down
6 changes: 6 additions & 0 deletions assuredworkloads/v1/assuredworkloads-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 9 additions & 1 deletion dialogflow/v3/dialogflow-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -4126,7 +4126,7 @@
}
}
},
"revision": "20230919",
"revision": "20231011",
"rootUrl": "https://dialogflow.googleapis.com/",
"schemas": {
"GoogleCloudDialogflowCxV3AdvancedSettings": {
Expand Down Expand Up @@ -7175,6 +7175,14 @@
"description": "Whether to disable webhook calls for this request.",
"type": "boolean"
},
"endUserMetadata": {
"additionalProperties": {
"description": "Properties of the object.",
"type": "any"
},
"description": "Optional. Information about the end-user to improve the relevance and accuracy of generative answers. This will be interpreted and used by a language model, so, for good results, the data should be self-descriptive, and in a simple structure. Example: ```json { \"subscription plan\": \"Business Premium Plus\", \"devices owned\": [ {\"model\": \"Google Pixel 7\"}, {\"model\": \"Google Pixel Tablet\"} ] } ```",
"type": "object"
},
"flowVersions": {
"description": "A list of flow versions to override for the request. Format: `projects//locations//agents//flows//versions/`. If version 1 of flow X is included in this list, the traffic of flow X will go through version 1 regardless of the version configuration in the environment. Each flow can have at most one version specified in this list.",
"items": {
Expand Down
9 changes: 9 additions & 0 deletions dialogflow/v3/dialogflow-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 9 additions & 1 deletion dialogflow/v3beta1/dialogflow-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -4126,7 +4126,7 @@
}
}
},
"revision": "20230919",
"revision": "20231011",
"rootUrl": "https://dialogflow.googleapis.com/",
"schemas": {
"GoogleCloudDialogflowCxV3AdvancedSettings": {
Expand Down Expand Up @@ -9358,6 +9358,14 @@
"description": "Whether to disable webhook calls for this request.",
"type": "boolean"
},
"endUserMetadata": {
"additionalProperties": {
"description": "Properties of the object.",
"type": "any"
},
"description": "Optional. Information about the end-user to improve the relevance and accuracy of generative answers. This will be interpreted and used by a language model, so, for good results, the data should be self-descriptive, and in a simple structure. Example: ```json { \"subscription plan\": \"Business Premium Plus\", \"devices owned\": [ {\"model\": \"Google Pixel 7\"}, {\"model\": \"Google Pixel Tablet\"} ] } ```",
"type": "object"
},
"flowVersions": {
"description": "A list of flow versions to override for the request. Format: `projects//locations//agents//flows//versions/`. If version 1 of flow X is included in this list, the traffic of flow X will go through version 1 regardless of the version configuration in the environment. Each flow can have at most one version specified in this list.",
"items": {
Expand Down
9 changes: 9 additions & 0 deletions dialogflow/v3beta1/dialogflow-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions playintegrity/v1/playintegrity-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@
}
}
},
"revision": "20231005",
"revision": "20231018",
"rootUrl": "https://playintegrity.googleapis.com/",
"schemas": {
"AccountActivity": {
Expand Down Expand Up @@ -371,7 +371,7 @@
"id": "UserRemediationDetails",
"properties": {
"remediation": {
"description": "Description of the user remediation action. Required.",
"description": "Description of the user remediation action.",
"enum": [
"UNKNOWN_USER_REMEDIATION",
"RESTORE_FACTORY_ROM",
Expand Down
2 changes: 1 addition & 1 deletion playintegrity/v1/playintegrity-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions testing/v1/testing-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -442,7 +442,7 @@
}
}
},
"revision": "20230908",
"revision": "20231017",
"rootUrl": "https://testing.googleapis.com/",
"schemas": {
"Account": {
Expand Down Expand Up @@ -1758,7 +1758,7 @@
"id": "ManualSharding",
"properties": {
"testTargetsForShard": {
"description": "Required. Group of packages, classes, and/or test methods to be run for each manually-created shard. You must specify at least one shard if this field is present. When you select one or more physical devices, the number of repeated test_targets_for_shard must be \u003c= 50. When you select one or more ARM virtual devices, it must be \u003c= 100. When you select only x86 virtual devices, it must be \u003c= 500.",
"description": "Required. Group of packages, classes, and/or test methods to be run for each manually-created shard. You must specify at least one shard if this field is present. When you select one or more physical devices, the number of repeated test_targets_for_shard must be \u003c= 50. When you select one or more ARM virtual devices, it must be \u003c= 200. When you select only x86 virtual devices, it must be \u003c= 500.",
"items": {
"$ref": "TestTargetsForShard"
},
Expand Down Expand Up @@ -2142,7 +2142,7 @@
"id": "SmartSharding",
"properties": {
"targetedShardDuration": {
"description": "The amount of time tests within a shard should take. Default: 300 seconds (5 minutes). The minimum allowed: 120 seconds (2 minutes). The shard count is dynamically set based on time, up to the maximum shard limit (described below). To guarantee at least one test case for each shard, the number of shards will not exceed the number of test cases. Shard duration will be exceeded if: - The maximum shard limit is reached and there is more calculated test time remaining to allocate into shards. - Any individual test is estimated to be longer than the targeted shard duration. Shard duration is not guaranteed because smart sharding uses test case history and default durations which may not be accurate. The rules for finding the test case timing records are: - If the service has processed a test case in the last 30 days, the record of the latest successful test case will be used. - For new test cases, the average duration of other known test cases will be used. - If there are no previous test case timing records available, the default test case duration is 15 seconds. Because the actual shard duration can exceed the targeted shard duration, we recommend that you set the targeted value at least 5 minutes less than the maximum allowed test timeout (45 minutes for physical devices and 60 minutes for virtual), or that you use the custom test timeout value that you set. This approach avoids cancelling the shard before all tests can finish. Note that there is a limit for maximum number of shards. When you select one or more physical devices, the number of shards must be \u003c= 50. When you select one or more ARM virtual devices, it must be \u003c= 100. When you select only x86 virtual devices, it must be \u003c= 500. To guarantee at least one test case for per shard, the number of shards will not exceed the number of test cases. Each shard created counts toward daily test quota.",
"description": "The amount of time tests within a shard should take. Default: 300 seconds (5 minutes). The minimum allowed: 120 seconds (2 minutes). The shard count is dynamically set based on time, up to the maximum shard limit (described below). To guarantee at least one test case for each shard, the number of shards will not exceed the number of test cases. Shard duration will be exceeded if: - The maximum shard limit is reached and there is more calculated test time remaining to allocate into shards. - Any individual test is estimated to be longer than the targeted shard duration. Shard duration is not guaranteed because smart sharding uses test case history and default durations which may not be accurate. The rules for finding the test case timing records are: - If the service has processed a test case in the last 30 days, the record of the latest successful test case will be used. - For new test cases, the average duration of other known test cases will be used. - If there are no previous test case timing records available, the default test case duration is 15 seconds. Because the actual shard duration can exceed the targeted shard duration, we recommend that you set the targeted value at least 5 minutes less than the maximum allowed test timeout (45 minutes for physical devices and 60 minutes for virtual), or that you use the custom test timeout value that you set. This approach avoids cancelling the shard before all tests can finish. Note that there is a limit for maximum number of shards. When you select one or more physical devices, the number of shards must be \u003c= 50. When you select one or more ARM virtual devices, it must be \u003c= 200. When you select only x86 virtual devices, it must be \u003c= 500. To guarantee at least one test case for per shard, the number of shards will not exceed the number of test cases. Each shard created counts toward daily test quota.",
"format": "google-duration",
"type": "string"
}
Expand Down Expand Up @@ -2741,7 +2741,7 @@
"id": "UniformSharding",
"properties": {
"numShards": {
"description": "Required. The total number of shards to create. This must always be a positive number that is no greater than the total number of test cases. When you select one or more physical devices, the number of shards must be \u003c= 50. When you select one or more ARM virtual devices, it must be \u003c= 100. When you select only x86 virtual devices, it must be \u003c= 500.",
"description": "Required. The total number of shards to create. This must always be a positive number that is no greater than the total number of test cases. When you select one or more physical devices, the number of shards must be \u003c= 50. When you select one or more ARM virtual devices, it must be \u003c= 200. When you select only x86 virtual devices, it must be \u003c= 500.",
"format": "int32",
"type": "integer"
}
Expand Down
6 changes: 3 additions & 3 deletions testing/v1/testing-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 199783c

Please sign in to comment.