Skip to content

Commit

Permalink
feat(all): auto-regenerate discovery clients (#2638)
Browse files Browse the repository at this point in the history
  • Loading branch information
yoshi-automation authored Jun 18, 2024
1 parent 324ae13 commit 0c868b2
Show file tree
Hide file tree
Showing 49 changed files with 34,247 additions and 451 deletions.
150 changes: 150 additions & 0 deletions api-list.json
Original file line number Diff line number Diff line change
Expand Up @@ -4116,6 +4116,156 @@
"documentationLink": "https://cloud.google.com/memorystore/",
"preferred": true
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:accounts_v1beta",
"name": "merchantapi",
"version": "accounts_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=accounts_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:conversions_v1beta",
"name": "merchantapi",
"version": "conversions_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=conversions_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:datasources_v1beta",
"name": "merchantapi",
"version": "datasources_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=datasources_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:inventories_v1beta",
"name": "merchantapi",
"version": "inventories_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=inventories_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:lfp_v1beta",
"name": "merchantapi",
"version": "lfp_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=lfp_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:notifications_v1beta",
"name": "merchantapi",
"version": "notifications_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=notifications_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:products_v1beta",
"name": "merchantapi",
"version": "products_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=products_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:promotions_v1beta",
"name": "merchantapi",
"version": "promotions_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=promotions_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:quota_v1beta",
"name": "merchantapi",
"version": "quota_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=quota_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": false
},
{
"kind": "discovery#directoryItem",
"id": "merchantapi:reports_v1beta",
"name": "merchantapi",
"version": "reports_v1beta",
"title": "Merchant API",
"description": "Programmatically manage your Merchant Center Accounts.",
"discoveryRestUrl": "https://merchantapi.googleapis.com/$discovery/rest?version=reports_v1beta",
"icons": {
"x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
"x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
},
"documentationLink": "https://developers.devsite.corp.google.com/merchant/api",
"preferred": true
},
{
"kind": "discovery#directoryItem",
"id": "metastore:v1alpha",
Expand Down
4 changes: 2 additions & 2 deletions bigtableadmin/v2/bigtableadmin-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -2194,7 +2194,7 @@
}
}
},
"revision": "20240429",
"revision": "20240522",
"rootUrl": "https://bigtableadmin.googleapis.com/",
"schemas": {
"AppProfile": {
Expand Down Expand Up @@ -4103,7 +4103,7 @@
"type": "object"
},
"Type": {
"description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. This might involve composing a series of steps into an \"encoding chain,\" for example to convert from INT64 -\u003e STRING -\u003e raw bytes. In most cases, a \"link\" in the encoding chain will be based an on existing GoogleSQL conversion function like `CAST`. Each link in the encoding chain also defines the following properties: * Natural sort: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: STRING values sort in the same order as their UTF-8 encodings. - Counterexample: Encoding INT64 to a fixed-width STRING does *not* preserve sort order when dealing with negative numbers. INT64(1) \u003e INT64(-1), but STRING(\"-00001\") \u003e STRING(\"00001). - The overall encoding chain sorts naturally if *every* link does. * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. - The overall encoding chain is self-delimiting if *any* link is. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
"description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. This might involve composing a series of steps into an \"encoding chain,\" for example to convert from INT64 -\u003e STRING -\u003e raw bytes. In most cases, a \"link\" in the encoding chain will be based an on existing GoogleSQL conversion function like `CAST`. Each link in the encoding chain also defines the following properties: * Natural sort: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING does *not* preserve sort order when dealing with negative numbers. INT64(1) \u003e INT64(-1), but STRING(\"-00001\") \u003e STRING(\"00001). - The overall encoding chain has this property if *every* link does. * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. - The overall encoding chain has this property if *any* link does. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
"id": "Type",
"properties": {
"aggregateType": {
Expand Down
10 changes: 5 additions & 5 deletions bigtableadmin/v2/bigtableadmin-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 binaryauthorization/v1/binaryauthorization-api.json
Original file line number Diff line number Diff line change
Expand Up @@ -742,7 +742,7 @@
}
}
},
"revision": "20240524",
"revision": "20240607",
"rootUrl": "https://binaryauthorization.googleapis.com/",
"schemas": {
"AdmissionRule": {
Expand Down Expand Up @@ -1342,7 +1342,7 @@
"id": "PkixPublicKey",
"properties": {
"keyId": {
"description": "Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If `key_id` is left blank and this `PkixPublicKey` is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If this `PkixPublicKey` is used in the context of a wrapper that has its own notion of key ID (e.g. `AttestorPublicKey`), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value.",
"description": "Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them. The ID must match exactly contents of the `key_id` field exactly. The ID may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If `key_id` is left blank and this `PkixPublicKey` is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If this `PkixPublicKey` is used in the context of a wrapper that has its own notion of key ID (e.g. `AttestorPublicKey`), then this field can either match that value exactly, or be left blank, in which case it behaves exactly as though it is equal to that wrapper value.",
"type": "string"
},
"publicKeyPem": {
Expand Down
18 changes: 9 additions & 9 deletions binaryauthorization/v1/binaryauthorization-gen.go

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

Loading

0 comments on commit 0c868b2

Please sign in to comment.