From ed29945fc80a66af8fc58acdbb71136101206f20 Mon Sep 17 00:00:00 2001 From: Yoshi Automation Bot Date: Sun, 15 Dec 2024 00:28:23 -0800 Subject: [PATCH] feat(all): auto-regenerate discovery clients (#2920) --- .../v1/bigqueryreservation-api.json | 10 +- .../v1/bigqueryreservation-gen.go | 29 +++--- chat/v1/chat-api.json | 10 +- chat/v1/chat-gen.go | 11 +-- config/v1/config-api.json | 9 +- config/v1/config-gen.go | 7 +- domains/v1alpha2/domains-api.json | 12 +-- domains/v1alpha2/domains-gen.go | 50 +++++----- domains/v1beta1/domains-api.json | 12 +-- domains/v1beta1/domains-gen.go | 50 +++++----- gkeonprem/v1/gkeonprem-api.json | 4 +- gkeonprem/v1/gkeonprem-gen.go | 2 +- .../v1/rapidmigrationassessment-api.json | 4 +- .../v1/rapidmigrationassessment-gen.go | 2 +- redis/v1beta1/redis-api.json | 22 ++++- redis/v1beta1/redis-gen.go | 8 ++ .../serviceconsumermanagement-api.json | 6 +- .../v1beta1/serviceconsumermanagement-gen.go | 12 ++- serviceusage/v1beta1/serviceusage-api.json | 6 +- serviceusage/v1beta1/serviceusage-gen.go | 12 ++- workloadmanager/v1/workloadmanager-api.json | 98 ++++++++++++++++++- workloadmanager/v1/workloadmanager-gen.go | 84 +++++++++++++++- 22 files changed, 337 insertions(+), 123 deletions(-) diff --git a/bigqueryreservation/v1/bigqueryreservation-api.json b/bigqueryreservation/v1/bigqueryreservation-api.json index af02bcda616..4b05710927e 100644 --- a/bigqueryreservation/v1/bigqueryreservation-api.json +++ b/bigqueryreservation/v1/bigqueryreservation-api.json @@ -935,7 +935,7 @@ } } }, - "revision": "20241110", + "revision": "20241209", "rootUrl": "https://bigqueryreservation.googleapis.com/", "schemas": { "Assignment": { @@ -1346,15 +1346,17 @@ "type": "string" }, "originalPrimaryLocation": { - "description": "Optional. The original primary location of the reservation which is set only during its creation and remains unchanged afterwards. It can be used by the customer to answer questions about disaster recovery billing. The field is output only for customers and should not be specified, however, the `google.api.field_behavior` is not set to `OUTPUT_ONLY` since these fields are set in rerouted requests sent across regions.", + "description": "Output only. The location where the reservation was originally created. This is set only during the failover reservation's creation. All billing charges for the failover reservation will be applied to this location.", + "readOnly": true, "type": "string" }, "primaryLocation": { - "description": "Optional. The primary location of the reservation. The field is only meaningful for a failover reservation that is used for managed disaster recovery. The field is output only for customers and should not be specified. However, the `google.api.field_behavior` is not set to `OUTPUT_ONLY` since these fields are set in rerouted requests sent across regions.", + "description": "Output only. The current location of the reservation's primary replica. This field is only set for reservations using the managed disaster recovery feature.", + "readOnly": true, "type": "string" }, "secondaryLocation": { - "description": "Optional. The secondary location of the reservation that is used for managed disaster recovery. Customers can set this in create/update reservation calls to create a failover reservation or convert a non-failover reservation to a failover reservation.", + "description": "Optional. The current location of the reservation's secondary replica. This field is only set for reservations using the managed disaster recovery feature. Users can set this in create reservation calls to create a failover reservation or in update reservation calls to convert a non-failover reservation to a failover reservation(or vice versa).", "type": "string" }, "slotCapacity": { diff --git a/bigqueryreservation/v1/bigqueryreservation-gen.go b/bigqueryreservation/v1/bigqueryreservation-gen.go index 8ea8c84af32..792b99c4362 100644 --- a/bigqueryreservation/v1/bigqueryreservation-gen.go +++ b/bigqueryreservation/v1/bigqueryreservation-gen.go @@ -698,25 +698,20 @@ type Reservation struct { // with a letter and must not end with a dash. Its maximum length is 64 // characters. Name string `json:"name,omitempty"` - // OriginalPrimaryLocation: Optional. The original primary location of the - // reservation which is set only during its creation and remains unchanged - // afterwards. It can be used by the customer to answer questions about - // disaster recovery billing. The field is output only for customers and should - // not be specified, however, the `google.api.field_behavior` is not set to - // `OUTPUT_ONLY` since these fields are set in rerouted requests sent across - // regions. + // OriginalPrimaryLocation: Output only. The location where the reservation was + // originally created. This is set only during the failover reservation's + // creation. All billing charges for the failover reservation will be applied + // to this location. OriginalPrimaryLocation string `json:"originalPrimaryLocation,omitempty"` - // PrimaryLocation: Optional. The primary location of the reservation. The - // field is only meaningful for a failover reservation that is used for managed - // disaster recovery. The field is output only for customers and should not be - // specified. However, the `google.api.field_behavior` is not set to - // `OUTPUT_ONLY` since these fields are set in rerouted requests sent across - // regions. + // PrimaryLocation: Output only. The current location of the reservation's + // primary replica. This field is only set for reservations using the managed + // disaster recovery feature. PrimaryLocation string `json:"primaryLocation,omitempty"` - // SecondaryLocation: Optional. The secondary location of the reservation that - // is used for managed disaster recovery. Customers can set this in - // create/update reservation calls to create a failover reservation or convert - // a non-failover reservation to a failover reservation. + // SecondaryLocation: Optional. The current location of the reservation's + // secondary replica. This field is only set for reservations using the managed + // disaster recovery feature. Users can set this in create reservation calls to + // create a failover reservation or in update reservation calls to convert a + // non-failover reservation to a failover reservation(or vice versa). SecondaryLocation string `json:"secondaryLocation,omitempty"` // SlotCapacity: Baseline slots available to this reservation. A slot is a unit // of computational power in BigQuery, and serves as the unit of parallelism. diff --git a/chat/v1/chat-api.json b/chat/v1/chat-api.json index 6e14f4eaedc..beef80415da 100644 --- a/chat/v1/chat-api.json +++ b/chat/v1/chat-api.json @@ -48,22 +48,22 @@ "description": "View members in Google Chat conversations." }, "https://www.googleapis.com/auth/chat.messages": { - "description": "See, compose, send, update, and delete messages as well as their message content; add, see, and delete reactions to messages." + "description": "See, compose, send, update, and delete messages and their associated attachments, and add, see, and delete reactions to messages." }, "https://www.googleapis.com/auth/chat.messages.create": { "description": "Compose and send messages in Google Chat" }, "https://www.googleapis.com/auth/chat.messages.reactions": { - "description": "See, add, and delete reactions as well as their reaction content to messages in Google Chat" + "description": "See, add, and delete reactions to messages in Google Chat" }, "https://www.googleapis.com/auth/chat.messages.reactions.create": { "description": "Add reactions to messages in Google Chat" }, "https://www.googleapis.com/auth/chat.messages.reactions.readonly": { - "description": "View reactions as well as their reaction content to messages in Google Chat" + "description": "View reactions to messages in Google Chat" }, "https://www.googleapis.com/auth/chat.messages.readonly": { - "description": "See messages as well as their reactions and message content in Google Chat" + "description": "See messages and their associated reactions and attachments in Google Chat" }, "https://www.googleapis.com/auth/chat.spaces": { "description": "Create conversations and spaces and see or update metadata (including history settings and access settings) in Google Chat" @@ -1344,7 +1344,7 @@ } } }, - "revision": "20241208", + "revision": "20241210", "rootUrl": "https://chat.googleapis.com/", "schemas": { "AccessSettings": { diff --git a/chat/v1/chat-gen.go b/chat/v1/chat-gen.go index ccdd648f97b..778ff77f647 100644 --- a/chat/v1/chat-gen.go +++ b/chat/v1/chat-gen.go @@ -155,24 +155,23 @@ const ( // View members in Google Chat conversations. ChatMembershipsReadonlyScope = "https://www.googleapis.com/auth/chat.memberships.readonly" - // See, compose, send, update, and delete messages as well as their message - // content; add, see, and delete reactions to messages. + // See, compose, send, update, and delete messages and their associated + // attachments, and add, see, and delete reactions to messages. ChatMessagesScope = "https://www.googleapis.com/auth/chat.messages" // Compose and send messages in Google Chat ChatMessagesCreateScope = "https://www.googleapis.com/auth/chat.messages.create" - // See, add, and delete reactions as well as their reaction content to messages - // in Google Chat + // See, add, and delete reactions to messages in Google Chat ChatMessagesReactionsScope = "https://www.googleapis.com/auth/chat.messages.reactions" // Add reactions to messages in Google Chat ChatMessagesReactionsCreateScope = "https://www.googleapis.com/auth/chat.messages.reactions.create" - // View reactions as well as their reaction content to messages in Google Chat + // View reactions to messages in Google Chat ChatMessagesReactionsReadonlyScope = "https://www.googleapis.com/auth/chat.messages.reactions.readonly" - // See messages as well as their reactions and message content in Google Chat + // See messages and their associated reactions and attachments in Google Chat ChatMessagesReadonlyScope = "https://www.googleapis.com/auth/chat.messages.readonly" // Create conversations and spaces and see or update metadata (including diff --git a/config/v1/config-api.json b/config/v1/config-api.json index 6d3cd686456..196835ba61e 100644 --- a/config/v1/config-api.json +++ b/config/v1/config-api.json @@ -1187,7 +1187,7 @@ } } }, - "revision": "20241205", + "revision": "20241211", "rootUrl": "https://config.googleapis.com/", "schemas": { "ApplyResults": { @@ -2556,7 +2556,7 @@ "additionalProperties": { "$ref": "TerraformVariable" }, - "description": "Input variable values for the Terraform blueprint.", + "description": "Optional. Input variable values for the Terraform blueprint.", "type": "object" } }, @@ -2568,7 +2568,8 @@ "properties": { "error": { "$ref": "Status", - "description": "Original error response from underlying Google API, if available." + "description": "Output only. Original error response from underlying Google API, if available.", + "readOnly": true }, "errorDescription": { "description": "A human-readable error description.", @@ -2606,7 +2607,7 @@ "id": "TerraformVariable", "properties": { "inputValue": { - "description": "Input variable value.", + "description": "Optional. Input variable value.", "type": "any" } }, diff --git a/config/v1/config-gen.go b/config/v1/config-gen.go index f39b4b7d5f5..e7adad4c192 100644 --- a/config/v1/config-gen.go +++ b/config/v1/config-gen.go @@ -1871,7 +1871,7 @@ type TerraformBlueprint struct { GcsSource string `json:"gcsSource,omitempty"` // GitSource: URI of a public Git repo. GitSource *GitSource `json:"gitSource,omitempty"` - // InputValues: Input variable values for the Terraform blueprint. + // InputValues: Optional. Input variable values for the Terraform blueprint. InputValues map[string]TerraformVariable `json:"inputValues,omitempty"` // ForceSendFields is a list of field names (e.g. "GcsSource") to // unconditionally include in API requests. By default, fields with empty or @@ -1893,7 +1893,8 @@ func (s TerraformBlueprint) MarshalJSON() ([]byte, error) { // TerraformError: Errors encountered during actuation using Terraform type TerraformError struct { - // Error: Original error response from underlying Google API, if available. + // Error: Output only. Original error response from underlying Google API, if + // available. Error *Status `json:"error,omitempty"` // ErrorDescription: A human-readable error description. ErrorDescription string `json:"errorDescription,omitempty"` @@ -1949,7 +1950,7 @@ func (s TerraformOutput) MarshalJSON() ([]byte, error) { // TerraformVariable: A Terraform input variable. type TerraformVariable struct { - // InputValue: Input variable value. + // InputValue: Optional. Input variable value. InputValue interface{} `json:"inputValue,omitempty"` // ForceSendFields is a list of field names (e.g. "InputValue") to // unconditionally include in API requests. By default, fields with empty or diff --git a/domains/v1alpha2/domains-api.json b/domains/v1alpha2/domains-api.json index 58c87055b98..f59dc7fb965 100644 --- a/domains/v1alpha2/domains-api.json +++ b/domains/v1alpha2/domains-api.json @@ -965,7 +965,7 @@ } } }, - "revision": "20240724", + "revision": "20241209", "rootUrl": "https://domains.googleapis.com/", "schemas": { "AuditConfig": { @@ -1939,18 +1939,18 @@ "type": "object" }, "PostalAddress": { - "description": "Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478", + "description": "Represents a postal address. For example for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created by user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, see: https://support.google.com/business/answer/6397478", "id": "PostalAddress", "properties": { "addressLines": { - "description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (e.g. \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (e.g. Japan), address_language is used to make it explicit (e.g. \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).", + "description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (For example \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (For example Japan), address_language is used to make it explicit (For example \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).", "items": { "type": "string" }, "type": "array" }, "administrativeArea": { - "description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (e.g. \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. E.g. in Switzerland this should be left unpopulated.", + "description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (For example \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. For example in Switzerland this should be left unpopulated.", "type": "string" }, "languageCode": { @@ -1966,7 +1966,7 @@ "type": "string" }, "postalCode": { - "description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (e.g. state/zip validation in the U.S.A.).", + "description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (For example state/zip validation in the U.S.A.).", "type": "string" }, "recipients": { @@ -1986,7 +1986,7 @@ "type": "integer" }, "sortingCode": { - "description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (e.g. \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (e.g. Côte d'Ivoire).", + "description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (For example \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (For example Côte d'Ivoire).", "type": "string" }, "sublocality": { diff --git a/domains/v1alpha2/domains-gen.go b/domains/v1alpha2/domains-gen.go index 955f1bcb1a9..5c775a50070 100644 --- a/domains/v1alpha2/domains-gen.go +++ b/domains/v1alpha2/domains-gen.go @@ -1583,42 +1583,43 @@ func (s Policy) MarshalJSON() ([]byte, error) { return gensupport.MarshalJSON(NoMethod(s), s.ForceSendFields, s.NullFields) } -// PostalAddress: Represents a postal address, e.g. for postal delivery or -// payments addresses. Given a postal address, a postal service can deliver +// PostalAddress: Represents a postal address. For example for postal delivery +// or payments addresses. Given a postal address, a postal service can deliver // items to a premise, P.O. Box or similar. It is not intended to model // geographical locations (roads, towns, mountains). In typical usage an -// address would be created via user input or from importing existing data, +// address would be created by user input or from importing existing data, // depending on the type of process. Advice on address input / editing: - Use // an internationalization-ready address widget such as // https://github.com/google/libaddressinput) - Users should not be presented // with UI elements for input or editing of fields outside countries where that -// field is used. For more guidance on how to use this schema, please see: +// field is used. For more guidance on how to use this schema, see: // https://support.google.com/business/answer/6397478 type PostalAddress struct { // AddressLines: Unstructured address lines describing the lower levels of an // address. Because values in address_lines do not have type information and - // may sometimes contain multiple values in a single field (e.g. "Austin, TX"), - // it is important that the line order is clear. The order of address lines - // should be "envelope order" for the country/region of the address. In places - // where this can vary (e.g. Japan), address_language is used to make it - // explicit (e.g. "ja" for large-to-small ordering and "ja-Latn" or "en" for - // small-to-large). This way, the most specific line of an address can be - // selected based on the language. The minimum permitted structural - // representation of an address consists of a region_code with all remaining - // information placed in the address_lines. It would be possible to format such - // an address very approximately without geocoding, but no semantic reasoning - // could be made about any of the address components until it was at least - // partially resolved. Creating an address only containing a region_code and - // address_lines, and then geocoding is the recommended way to handle + // may sometimes contain multiple values in a single field (For example + // "Austin, TX"), it is important that the line order is clear. The order of + // address lines should be "envelope order" for the country/region of the + // address. In places where this can vary (For example Japan), address_language + // is used to make it explicit (For example "ja" for large-to-small ordering + // and "ja-Latn" or "en" for small-to-large). This way, the most specific line + // of an address can be selected based on the language. The minimum permitted + // structural representation of an address consists of a region_code with all + // remaining information placed in the address_lines. It would be possible to + // format such an address very approximately without geocoding, but no semantic + // reasoning could be made about any of the address components until it was at + // least partially resolved. Creating an address only containing a region_code + // and address_lines, and then geocoding is the recommended way to handle // completely unstructured addresses (as opposed to guessing which parts of the // address should be localities or administrative areas). AddressLines []string `json:"addressLines,omitempty"` // AdministrativeArea: Optional. Highest administrative subdivision which is // used for postal addresses of a country or region. For example, this can be a // state, a province, an oblast, or a prefecture. Specifically, for Spain this - // is the province and not the autonomous community (e.g. "Barcelona" and not - // "Catalonia"). Many countries don't use an administrative area in postal - // addresses. E.g. in Switzerland this should be left unpopulated. + // is the province and not the autonomous community (For example "Barcelona" + // and not "Catalonia"). Many countries don't use an administrative area in + // postal addresses. For example in Switzerland this should be left + // unpopulated. AdministrativeArea string `json:"administrativeArea,omitempty"` // LanguageCode: Optional. BCP-47 language code of the contents of this address // (if known). This is often the UI language of the input form or is expected @@ -1638,7 +1639,7 @@ type PostalAddress struct { Organization string `json:"organization,omitempty"` // PostalCode: Optional. Postal code of the address. Not all countries use or // require postal codes to be present, but where they are used, they may - // trigger additional validation with other parts of the address (e.g. + // trigger additional validation with other parts of the address (For example // state/zip validation in the U.S.A.). PostalCode string `json:"postalCode,omitempty"` // Recipients: Optional. The recipient at the address. This field may, under @@ -1657,9 +1658,10 @@ type PostalAddress struct { Revision int64 `json:"revision,omitempty"` // SortingCode: Optional. Additional, country-specific, sorting code. This is // not used in most regions. Where it is used, the value is either a string - // like "CEDEX", optionally followed by a number (e.g. "CEDEX 7"), or just a - // number alone, representing the "sector code" (Jamaica), "delivery area - // indicator" (Malawi) or "post office indicator" (e.g. Côte d'Ivoire). + // like "CEDEX", optionally followed by a number (For example "CEDEX 7"), or + // just a number alone, representing the "sector code" (Jamaica), "delivery + // area indicator" (Malawi) or "post office indicator" (For example Côte + // d'Ivoire). SortingCode string `json:"sortingCode,omitempty"` // Sublocality: Optional. Sublocality of the address. For example, this can be // neighborhoods, boroughs, districts. diff --git a/domains/v1beta1/domains-api.json b/domains/v1beta1/domains-api.json index 583f4100062..0fb31527446 100644 --- a/domains/v1beta1/domains-api.json +++ b/domains/v1beta1/domains-api.json @@ -965,7 +965,7 @@ } } }, - "revision": "20240724", + "revision": "20241209", "rootUrl": "https://domains.googleapis.com/", "schemas": { "AuditConfig": { @@ -1939,18 +1939,18 @@ "type": "object" }, "PostalAddress": { - "description": "Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478", + "description": "Represents a postal address. For example for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created by user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, see: https://support.google.com/business/answer/6397478", "id": "PostalAddress", "properties": { "addressLines": { - "description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (e.g. \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (e.g. Japan), address_language is used to make it explicit (e.g. \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).", + "description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (For example \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (For example Japan), address_language is used to make it explicit (For example \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).", "items": { "type": "string" }, "type": "array" }, "administrativeArea": { - "description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (e.g. \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. E.g. in Switzerland this should be left unpopulated.", + "description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (For example \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. For example in Switzerland this should be left unpopulated.", "type": "string" }, "languageCode": { @@ -1966,7 +1966,7 @@ "type": "string" }, "postalCode": { - "description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (e.g. state/zip validation in the U.S.A.).", + "description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (For example state/zip validation in the U.S.A.).", "type": "string" }, "recipients": { @@ -1986,7 +1986,7 @@ "type": "integer" }, "sortingCode": { - "description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (e.g. \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (e.g. Côte d'Ivoire).", + "description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (For example \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (For example Côte d'Ivoire).", "type": "string" }, "sublocality": { diff --git a/domains/v1beta1/domains-gen.go b/domains/v1beta1/domains-gen.go index 137a2b127de..93d5dd69662 100644 --- a/domains/v1beta1/domains-gen.go +++ b/domains/v1beta1/domains-gen.go @@ -1583,42 +1583,43 @@ func (s Policy) MarshalJSON() ([]byte, error) { return gensupport.MarshalJSON(NoMethod(s), s.ForceSendFields, s.NullFields) } -// PostalAddress: Represents a postal address, e.g. for postal delivery or -// payments addresses. Given a postal address, a postal service can deliver +// PostalAddress: Represents a postal address. For example for postal delivery +// or payments addresses. Given a postal address, a postal service can deliver // items to a premise, P.O. Box or similar. It is not intended to model // geographical locations (roads, towns, mountains). In typical usage an -// address would be created via user input or from importing existing data, +// address would be created by user input or from importing existing data, // depending on the type of process. Advice on address input / editing: - Use // an internationalization-ready address widget such as // https://github.com/google/libaddressinput) - Users should not be presented // with UI elements for input or editing of fields outside countries where that -// field is used. For more guidance on how to use this schema, please see: +// field is used. For more guidance on how to use this schema, see: // https://support.google.com/business/answer/6397478 type PostalAddress struct { // AddressLines: Unstructured address lines describing the lower levels of an // address. Because values in address_lines do not have type information and - // may sometimes contain multiple values in a single field (e.g. "Austin, TX"), - // it is important that the line order is clear. The order of address lines - // should be "envelope order" for the country/region of the address. In places - // where this can vary (e.g. Japan), address_language is used to make it - // explicit (e.g. "ja" for large-to-small ordering and "ja-Latn" or "en" for - // small-to-large). This way, the most specific line of an address can be - // selected based on the language. The minimum permitted structural - // representation of an address consists of a region_code with all remaining - // information placed in the address_lines. It would be possible to format such - // an address very approximately without geocoding, but no semantic reasoning - // could be made about any of the address components until it was at least - // partially resolved. Creating an address only containing a region_code and - // address_lines, and then geocoding is the recommended way to handle + // may sometimes contain multiple values in a single field (For example + // "Austin, TX"), it is important that the line order is clear. The order of + // address lines should be "envelope order" for the country/region of the + // address. In places where this can vary (For example Japan), address_language + // is used to make it explicit (For example "ja" for large-to-small ordering + // and "ja-Latn" or "en" for small-to-large). This way, the most specific line + // of an address can be selected based on the language. The minimum permitted + // structural representation of an address consists of a region_code with all + // remaining information placed in the address_lines. It would be possible to + // format such an address very approximately without geocoding, but no semantic + // reasoning could be made about any of the address components until it was at + // least partially resolved. Creating an address only containing a region_code + // and address_lines, and then geocoding is the recommended way to handle // completely unstructured addresses (as opposed to guessing which parts of the // address should be localities or administrative areas). AddressLines []string `json:"addressLines,omitempty"` // AdministrativeArea: Optional. Highest administrative subdivision which is // used for postal addresses of a country or region. For example, this can be a // state, a province, an oblast, or a prefecture. Specifically, for Spain this - // is the province and not the autonomous community (e.g. "Barcelona" and not - // "Catalonia"). Many countries don't use an administrative area in postal - // addresses. E.g. in Switzerland this should be left unpopulated. + // is the province and not the autonomous community (For example "Barcelona" + // and not "Catalonia"). Many countries don't use an administrative area in + // postal addresses. For example in Switzerland this should be left + // unpopulated. AdministrativeArea string `json:"administrativeArea,omitempty"` // LanguageCode: Optional. BCP-47 language code of the contents of this address // (if known). This is often the UI language of the input form or is expected @@ -1638,7 +1639,7 @@ type PostalAddress struct { Organization string `json:"organization,omitempty"` // PostalCode: Optional. Postal code of the address. Not all countries use or // require postal codes to be present, but where they are used, they may - // trigger additional validation with other parts of the address (e.g. + // trigger additional validation with other parts of the address (For example // state/zip validation in the U.S.A.). PostalCode string `json:"postalCode,omitempty"` // Recipients: Optional. The recipient at the address. This field may, under @@ -1657,9 +1658,10 @@ type PostalAddress struct { Revision int64 `json:"revision,omitempty"` // SortingCode: Optional. Additional, country-specific, sorting code. This is // not used in most regions. Where it is used, the value is either a string - // like "CEDEX", optionally followed by a number (e.g. "CEDEX 7"), or just a - // number alone, representing the "sector code" (Jamaica), "delivery area - // indicator" (Malawi) or "post office indicator" (e.g. Côte d'Ivoire). + // like "CEDEX", optionally followed by a number (For example "CEDEX 7"), or + // just a number alone, representing the "sector code" (Jamaica), "delivery + // area indicator" (Malawi) or "post office indicator" (For example Côte + // d'Ivoire). SortingCode string `json:"sortingCode,omitempty"` // Sublocality: Optional. Sublocality of the address. For example, this can be // neighborhoods, boroughs, districts. diff --git a/gkeonprem/v1/gkeonprem-api.json b/gkeonprem/v1/gkeonprem-api.json index 803c7e8525d..cb927ddd288 100644 --- a/gkeonprem/v1/gkeonprem-api.json +++ b/gkeonprem/v1/gkeonprem-api.json @@ -1597,7 +1597,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/projects/{projectsId}/locations/{locationsId}/operations/{operationsId}:cancel", "httpMethod": "POST", "id": "gkeonprem.projects.locations.operations.cancel", @@ -3094,7 +3094,7 @@ } } }, - "revision": "20241110", + "revision": "20241204", "rootUrl": "https://gkeonprem.googleapis.com/", "schemas": { "Authorization": { diff --git a/gkeonprem/v1/gkeonprem-gen.go b/gkeonprem/v1/gkeonprem-gen.go index 4bbb040d18a..6a8677102c6 100644 --- a/gkeonprem/v1/gkeonprem-gen.go +++ b/gkeonprem/v1/gkeonprem-gen.go @@ -10335,7 +10335,7 @@ type ProjectsLocationsOperationsCancelCall struct { // 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 +// Operation.error value with a google.rpc.Status.code of `1`, corresponding to // `Code.CANCELLED`. // // - name: The name of the operation resource to be cancelled. diff --git a/rapidmigrationassessment/v1/rapidmigrationassessment-api.json b/rapidmigrationassessment/v1/rapidmigrationassessment-api.json index ec24a1154b5..49bd859772d 100644 --- a/rapidmigrationassessment/v1/rapidmigrationassessment-api.json +++ b/rapidmigrationassessment/v1/rapidmigrationassessment-api.json @@ -508,7 +508,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/projects/{projectsId}/locations/{locationsId}/operations/{operationsId}:cancel", "httpMethod": "POST", "id": "rapidmigrationassessment.projects.locations.operations.cancel", @@ -633,7 +633,7 @@ } } }, - "revision": "20230824", + "revision": "20241211", "rootUrl": "https://rapidmigrationassessment.googleapis.com/", "schemas": { "Annotation": { diff --git a/rapidmigrationassessment/v1/rapidmigrationassessment-gen.go b/rapidmigrationassessment/v1/rapidmigrationassessment-gen.go index 17d1c42480d..4b405165954 100644 --- a/rapidmigrationassessment/v1/rapidmigrationassessment-gen.go +++ b/rapidmigrationassessment/v1/rapidmigrationassessment-gen.go @@ -2114,7 +2114,7 @@ type ProjectsLocationsOperationsCancelCall struct { // 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 +// Operation.error value with a google.rpc.Status.code of `1`, corresponding to // `Code.CANCELLED`. // // - name: The name of the operation resource to be cancelled. diff --git a/redis/v1beta1/redis-api.json b/redis/v1beta1/redis-api.json index bfe575d3b69..5ff1c381f1d 100644 --- a/redis/v1beta1/redis-api.json +++ b/redis/v1beta1/redis-api.json @@ -1067,7 +1067,7 @@ } } }, - "revision": "20241203", + "revision": "20241212", "rootUrl": "https://redis.googleapis.com/", "schemas": { "AOFConfig": { @@ -2082,7 +2082,9 @@ "SIGNAL_TYPE_SUPERUSER_WRITING_TO_USER_TABLES", "SIGNAL_TYPE_USER_GRANTED_ALL_PERMISSIONS", "SIGNAL_TYPE_DATA_EXPORT_TO_EXTERNAL_CLOUD_STORAGE_BUCKET", - "SIGNAL_TYPE_DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET" + "SIGNAL_TYPE_DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET", + "SIGNAL_TYPE_WEAK_PASSWORD_HASH_ALGORITHM", + "SIGNAL_TYPE_NO_USER_PASSWORD_POLICY" ], "enumDeprecated": [ false, @@ -2163,6 +2165,8 @@ false, false, false, + false, + false, false ], "enumDescriptions": [ @@ -2244,7 +2248,9 @@ "Detects events where a Cloud SQL superuser (postgres for PostgreSQL servers or root for MySQL users) writes to non-system tables.", "Detects events where a database user or role has been granted all privileges to a database, or to all tables, procedures, or functions in a schema.", "Detects if database instance data exported to a Cloud Storage bucket outside of the organization.", - "Detects if database instance data exported to a Cloud Storage bucket that is owned by the organization and is publicly accessible." + "Detects if database instance data exported to a Cloud Storage bucket that is owned by the organization and is publicly accessible.", + "Detects if a database instance is using a weak password hash algorithm.", + "Detects if a database instance has no user password policy set." ], "type": "string" }, @@ -2615,7 +2621,9 @@ "SIGNAL_TYPE_SUPERUSER_WRITING_TO_USER_TABLES", "SIGNAL_TYPE_USER_GRANTED_ALL_PERMISSIONS", "SIGNAL_TYPE_DATA_EXPORT_TO_EXTERNAL_CLOUD_STORAGE_BUCKET", - "SIGNAL_TYPE_DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET" + "SIGNAL_TYPE_DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET", + "SIGNAL_TYPE_WEAK_PASSWORD_HASH_ALGORITHM", + "SIGNAL_TYPE_NO_USER_PASSWORD_POLICY" ], "enumDeprecated": [ false, @@ -2696,6 +2704,8 @@ false, false, false, + false, + false, false ], "enumDescriptions": [ @@ -2777,7 +2787,9 @@ "Detects events where a Cloud SQL superuser (postgres for PostgreSQL servers or root for MySQL users) writes to non-system tables.", "Detects events where a database user or role has been granted all privileges to a database, or to all tables, procedures, or functions in a schema.", "Detects if database instance data exported to a Cloud Storage bucket outside of the organization.", - "Detects if database instance data exported to a Cloud Storage bucket that is owned by the organization and is publicly accessible." + "Detects if database instance data exported to a Cloud Storage bucket that is owned by the organization and is publicly accessible.", + "Detects if a database instance is using a weak password hash algorithm.", + "Detects if a database instance has no user password policy set." ], "type": "string" } diff --git a/redis/v1beta1/redis-gen.go b/redis/v1beta1/redis-gen.go index db928d4358f..b440a67ca88 100644 --- a/redis/v1beta1/redis-gen.go +++ b/redis/v1beta1/redis-gen.go @@ -1357,6 +1357,10 @@ type DatabaseResourceHealthSignalData struct { // "SIGNAL_TYPE_DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET" - Detects if // database instance data exported to a Cloud Storage bucket that is owned by // the organization and is publicly accessible. + // "SIGNAL_TYPE_WEAK_PASSWORD_HASH_ALGORITHM" - Detects if a database + // instance is using a weak password hash algorithm. + // "SIGNAL_TYPE_NO_USER_PASSWORD_POLICY" - Detects if a database instance has + // no user password policy set. SignalType string `json:"signalType,omitempty"` // Possible values: // "STATE_UNSPECIFIED" - Unspecified state. @@ -1786,6 +1790,10 @@ type DatabaseResourceRecommendationSignalData struct { // "SIGNAL_TYPE_DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET" - Detects if // database instance data exported to a Cloud Storage bucket that is owned by // the organization and is publicly accessible. + // "SIGNAL_TYPE_WEAK_PASSWORD_HASH_ALGORITHM" - Detects if a database + // instance is using a weak password hash algorithm. + // "SIGNAL_TYPE_NO_USER_PASSWORD_POLICY" - Detects if a database instance has + // no user password policy set. SignalType string `json:"signalType,omitempty"` // ForceSendFields is a list of field names (e.g. "AdditionalMetadata") to // unconditionally include in API requests. By default, fields with empty or diff --git a/serviceconsumermanagement/v1beta1/serviceconsumermanagement-api.json b/serviceconsumermanagement/v1beta1/serviceconsumermanagement-api.json index 29662e61011..63b55773ae7 100644 --- a/serviceconsumermanagement/v1beta1/serviceconsumermanagement-api.json +++ b/serviceconsumermanagement/v1beta1/serviceconsumermanagement-api.json @@ -715,7 +715,7 @@ } } }, - "revision": "20241115", + "revision": "20241205", "rootUrl": "https://serviceconsumermanagement.googleapis.com/", "schemas": { "Api": { @@ -1218,6 +1218,10 @@ "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: \u003e The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: \u003e ... - selector: google.calendar.Calendar.Put description: \u003e ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.", "id": "Documentation", "properties": { + "additionalIamInfo": { + "description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.", + "type": "string" + }, "documentationRootUrl": { "description": "The URL to the root of documentation.", "type": "string" diff --git a/serviceconsumermanagement/v1beta1/serviceconsumermanagement-gen.go b/serviceconsumermanagement/v1beta1/serviceconsumermanagement-gen.go index 9703b869bc0..52c7d83e580 100644 --- a/serviceconsumermanagement/v1beta1/serviceconsumermanagement-gen.go +++ b/serviceconsumermanagement/v1beta1/serviceconsumermanagement-gen.go @@ -995,6 +995,10 @@ func (s CustomHttpPattern) MarshalJSON() ([]byte, error) { // directive `suppress_warning` does not directly affect documentation and is // documented together with service config validation. type Documentation struct { + // AdditionalIamInfo: Optional information about the IAM configuration. This is + // typically used to link to documentation about a product's IAM roles and + // permissions. + AdditionalIamInfo string `json:"additionalIamInfo,omitempty"` // DocumentationRootUrl: The URL to the root of documentation. DocumentationRootUrl string `json:"documentationRootUrl,omitempty"` // Overview: Declares a single overview page. For example: documentation: @@ -1021,15 +1025,15 @@ type Documentation struct { // plain text. It becomes the overview of the service displayed in Google Cloud // Console. NOTE: This field is equivalent to the standard field `description`. Summary string `json:"summary,omitempty"` - // ForceSendFields is a list of field names (e.g. "DocumentationRootUrl") to + // ForceSendFields is a list of field names (e.g. "AdditionalIamInfo") to // unconditionally include in API requests. By default, fields with empty or // default values are omitted from API requests. See // https://pkg.go.dev/google.golang.org/api#hdr-ForceSendFields for more // details. ForceSendFields []string `json:"-"` - // NullFields is a list of field names (e.g. "DocumentationRootUrl") to include - // in API requests with the JSON null value. By default, fields with empty - // values are omitted from API requests. See + // NullFields is a list of field names (e.g. "AdditionalIamInfo") to include in + // API requests with the JSON null value. By default, fields with empty values + // are omitted from API requests. See // https://pkg.go.dev/google.golang.org/api#hdr-NullFields for more details. NullFields []string `json:"-"` } diff --git a/serviceusage/v1beta1/serviceusage-api.json b/serviceusage/v1beta1/serviceusage-api.json index eb0f5b12b54..e3a1daf1824 100644 --- a/serviceusage/v1beta1/serviceusage-api.json +++ b/serviceusage/v1beta1/serviceusage-api.json @@ -964,7 +964,7 @@ } } }, - "revision": "20241115", + "revision": "20241205", "rootUrl": "https://serviceusage.googleapis.com/", "schemas": { "AddEnableRulesMetadata": { @@ -1808,6 +1808,10 @@ "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: \u003e The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: \u003e ... - selector: google.calendar.Calendar.Put description: \u003e ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.", "id": "Documentation", "properties": { + "additionalIamInfo": { + "description": "Optional information about the IAM configuration. This is typically used to link to documentation about a product's IAM roles and permissions.", + "type": "string" + }, "documentationRootUrl": { "description": "The URL to the root of documentation.", "type": "string" diff --git a/serviceusage/v1beta1/serviceusage-gen.go b/serviceusage/v1beta1/serviceusage-gen.go index ff7ef98b877..c32c8260d60 100644 --- a/serviceusage/v1beta1/serviceusage-gen.go +++ b/serviceusage/v1beta1/serviceusage-gen.go @@ -1457,6 +1457,10 @@ func (s DisableServiceResponse) MarshalJSON() ([]byte, error) { // directive `suppress_warning` does not directly affect documentation and is // documented together with service config validation. type Documentation struct { + // AdditionalIamInfo: Optional information about the IAM configuration. This is + // typically used to link to documentation about a product's IAM roles and + // permissions. + AdditionalIamInfo string `json:"additionalIamInfo,omitempty"` // DocumentationRootUrl: The URL to the root of documentation. DocumentationRootUrl string `json:"documentationRootUrl,omitempty"` // Overview: Declares a single overview page. For example: documentation: @@ -1483,15 +1487,15 @@ type Documentation struct { // plain text. It becomes the overview of the service displayed in Google Cloud // Console. NOTE: This field is equivalent to the standard field `description`. Summary string `json:"summary,omitempty"` - // ForceSendFields is a list of field names (e.g. "DocumentationRootUrl") to + // ForceSendFields is a list of field names (e.g. "AdditionalIamInfo") to // unconditionally include in API requests. By default, fields with empty or // default values are omitted from API requests. See // https://pkg.go.dev/google.golang.org/api#hdr-ForceSendFields for more // details. ForceSendFields []string `json:"-"` - // NullFields is a list of field names (e.g. "DocumentationRootUrl") to include - // in API requests with the JSON null value. By default, fields with empty - // values are omitted from API requests. See + // NullFields is a list of field names (e.g. "AdditionalIamInfo") to include in + // API requests with the JSON null value. By default, fields with empty values + // are omitted from API requests. See // https://pkg.go.dev/google.golang.org/api#hdr-NullFields for more details. NullFields []string `json:"-"` } diff --git a/workloadmanager/v1/workloadmanager-api.json b/workloadmanager/v1/workloadmanager-api.json index 50303bde227..bae04fa0110 100644 --- a/workloadmanager/v1/workloadmanager-api.json +++ b/workloadmanager/v1/workloadmanager-api.json @@ -597,7 +597,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/projects/{projectsId}/locations/{locationsId}/operations/{operationsId}:cancel", "httpMethod": "POST", "id": "workloadmanager.projects.locations.operations.cancel", @@ -772,7 +772,7 @@ } } }, - "revision": "20241016", + "revision": "20241209", "rootUrl": "https://workloadmanager.googleapis.com/", "schemas": { "AgentCommand": { @@ -857,6 +857,24 @@ "description": "Description of the Evaluation", "type": "string" }, + "evaluationType": { + "description": "Evaluation type", + "enum": [ + "EVALUATION_TYPE_UNSPECIFIED", + "SAP", + "SQL_SERVER", + "OTHER", + "SCC_IAC" + ], + "enumDescriptions": [ + "Not specified", + "SAP best practices", + "SQL best practices", + "Customized best practices", + "SCC IaC (Infra as Code) best practices" + ], + "type": "string" + }, "labels": { "additionalProperties": { "type": "string" @@ -952,6 +970,11 @@ "readOnly": true, "type": "array" }, + "resultSummary": { + "$ref": "Summary", + "description": "Output only. [Output only] Result summary", + "readOnly": true + }, "ruleResults": { "description": "Output only. execution result summary per rule", "items": { @@ -1122,6 +1145,10 @@ "sqlserverValidation": { "$ref": "SqlserverValidation", "description": "The insights data for the sqlserver workload validation." + }, + "torsoValidation": { + "$ref": "TorsoValidation", + "description": "The insights data for workload validation of torso workloads." } }, "type": "object" @@ -2240,6 +2267,73 @@ }, "type": "object" }, + "Summary": { + "description": "Message for execution summary", + "id": "Summary", + "properties": { + "failures": { + "description": "Output only. Number of failures", + "format": "int64", + "readOnly": true, + "type": "string" + }, + "newFailures": { + "description": "Output only. Number of new failures compared to the previous execution", + "format": "int64", + "readOnly": true, + "type": "string" + }, + "newFixes": { + "description": "Output only. Number of new fixes compared to the previous execution", + "format": "int64", + "readOnly": true, + "type": "string" + } + }, + "type": "object" + }, + "TorsoValidation": { + "description": "The schema of torso workload validation data.", + "id": "TorsoValidation", + "properties": { + "agentVersion": { + "description": "Required. agent_version lists the version of the agent that collected this data.", + "type": "string" + }, + "instanceName": { + "description": "Required. instance_name lists the human readable name of the instance that the data comes from.", + "type": "string" + }, + "projectId": { + "description": "Required. project_id lists the human readable cloud project that the data comes from.", + "type": "string" + }, + "validationDetails": { + "additionalProperties": { + "type": "string" + }, + "description": "Required. validation_details contains the pairs of validation data: field name \u0026 field value.", + "type": "object" + }, + "workloadType": { + "description": "Required. workload_type specifies the type of torso workload.", + "enum": [ + "WORKLOAD_TYPE_UNSPECIFIED", + "MYSQL", + "ORACLE", + "REDIS" + ], + "enumDescriptions": [ + "Unspecified workload type.", + "MySQL workload.", + "Oracle workload.", + "Redis workload." + ], + "type": "string" + } + }, + "type": "object" + }, "ViolationDetails": { "description": "Message describing the violation in an evaluation result.", "id": "ViolationDetails", diff --git a/workloadmanager/v1/workloadmanager-gen.go b/workloadmanager/v1/workloadmanager-gen.go index 9d494df8d97..763ec01efa3 100644 --- a/workloadmanager/v1/workloadmanager-gen.go +++ b/workloadmanager/v1/workloadmanager-gen.go @@ -358,6 +358,15 @@ type Evaluation struct { CustomRulesBucket string `json:"customRulesBucket,omitempty"` // Description: Description of the Evaluation Description string `json:"description,omitempty"` + // EvaluationType: Evaluation type + // + // Possible values: + // "EVALUATION_TYPE_UNSPECIFIED" - Not specified + // "SAP" - SAP best practices + // "SQL_SERVER" - SQL best practices + // "OTHER" - Customized best practices + // "SCC_IAC" - SCC IaC (Infra as Code) best practices + EvaluationType string `json:"evaluationType,omitempty"` // Labels: Labels as key value pairs Labels map[string]string `json:"labels,omitempty"` // Name: name of resource names have the form @@ -416,6 +425,8 @@ type Execution struct { Name string `json:"name,omitempty"` // Notices: Output only. Additional information generated by the execution Notices []*Notice `json:"notices,omitempty"` + // ResultSummary: Output only. [Output only] Result summary + ResultSummary *Summary `json:"resultSummary,omitempty"` // RuleResults: Output only. execution result summary per rule RuleResults []*RuleExecutionResult `json:"ruleResults,omitempty"` // RunType: type represent whether the execution executed directly by user or @@ -571,6 +582,9 @@ type Insight struct { // SqlserverValidation: The insights data for the sqlserver workload // validation. SqlserverValidation *SqlserverValidation `json:"sqlserverValidation,omitempty"` + // TorsoValidation: The insights data for workload validation of torso + // workloads. + TorsoValidation *TorsoValidation `json:"torsoValidation,omitempty"` // ForceSendFields is a list of field names (e.g. "InstanceId") to // unconditionally include in API requests. By default, fields with empty or // default values are omitted from API requests. See @@ -1819,6 +1833,74 @@ func (s Status) MarshalJSON() ([]byte, error) { return gensupport.MarshalJSON(NoMethod(s), s.ForceSendFields, s.NullFields) } +// Summary: Message for execution summary +type Summary struct { + // Failures: Output only. Number of failures + Failures int64 `json:"failures,omitempty,string"` + // NewFailures: Output only. Number of new failures compared to the previous + // execution + NewFailures int64 `json:"newFailures,omitempty,string"` + // NewFixes: Output only. Number of new fixes compared to the previous + // execution + NewFixes int64 `json:"newFixes,omitempty,string"` + // ForceSendFields is a list of field names (e.g. "Failures") to + // unconditionally include in API requests. By default, fields with empty or + // default values are omitted from API requests. See + // https://pkg.go.dev/google.golang.org/api#hdr-ForceSendFields for more + // details. + ForceSendFields []string `json:"-"` + // NullFields is a list of field names (e.g. "Failures") to include in API + // requests with the JSON null value. By default, fields with empty values are + // omitted from API requests. See + // https://pkg.go.dev/google.golang.org/api#hdr-NullFields for more details. + NullFields []string `json:"-"` +} + +func (s Summary) MarshalJSON() ([]byte, error) { + type NoMethod Summary + return gensupport.MarshalJSON(NoMethod(s), s.ForceSendFields, s.NullFields) +} + +// TorsoValidation: The schema of torso workload validation data. +type TorsoValidation struct { + // AgentVersion: Required. agent_version lists the version of the agent that + // collected this data. + AgentVersion string `json:"agentVersion,omitempty"` + // InstanceName: Required. instance_name lists the human readable name of the + // instance that the data comes from. + InstanceName string `json:"instanceName,omitempty"` + // ProjectId: Required. project_id lists the human readable cloud project that + // the data comes from. + ProjectId string `json:"projectId,omitempty"` + // ValidationDetails: Required. validation_details contains the pairs of + // validation data: field name & field value. + ValidationDetails map[string]string `json:"validationDetails,omitempty"` + // WorkloadType: Required. workload_type specifies the type of torso workload. + // + // Possible values: + // "WORKLOAD_TYPE_UNSPECIFIED" - Unspecified workload type. + // "MYSQL" - MySQL workload. + // "ORACLE" - Oracle workload. + // "REDIS" - Redis workload. + WorkloadType string `json:"workloadType,omitempty"` + // ForceSendFields is a list of field names (e.g. "AgentVersion") to + // unconditionally include in API requests. By default, fields with empty or + // default values are omitted from API requests. See + // https://pkg.go.dev/google.golang.org/api#hdr-ForceSendFields for more + // details. + ForceSendFields []string `json:"-"` + // NullFields is a list of field names (e.g. "AgentVersion") to include in API + // requests with the JSON null value. By default, fields with empty values are + // omitted from API requests. See + // https://pkg.go.dev/google.golang.org/api#hdr-NullFields for more details. + NullFields []string `json:"-"` +} + +func (s TorsoValidation) MarshalJSON() ([]byte, error) { + type NoMethod TorsoValidation + return gensupport.MarshalJSON(NoMethod(s), s.ForceSendFields, s.NullFields) +} + // ViolationDetails: Message describing the violation in an evaluation result. type ViolationDetails struct { // Asset: The name of the asset. @@ -3554,7 +3636,7 @@ type ProjectsLocationsOperationsCancelCall struct { // 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 +// Operation.error value with a google.rpc.Status.code of `1`, corresponding to // `Code.CANCELLED`. // // - name: The name of the operation resource to be cancelled.