google-api-python-client 2.160.0__py2.py3-none-any.whl → 2.162.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/containeranalysis.v1beta1.json

@@ -1711,7 +1711,7 @@
 }
 }
 },
-"revision": "20240924",
+"revision": "20250207",
 "rootUrl": "https://containeranalysis.googleapis.com/",
 "schemas": {
 "AliasContext": {
@@ -2714,6 +2714,13 @@
 "description": "Artifacts produced by a build that should be uploaded upon successful completion of all build steps.",
 "id": "ContaineranalysisGoogleDevtoolsCloudbuildV1Artifacts",
 "properties": {
+"goModules": {
+"description": "Optional. A list of Go modules to be uploaded to Artifact Registry upon successful completion of all build steps. If any objects fail to be pushed, the build is marked FAILURE.",
+"items": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1ArtifactsGoModule"
+},
+"type": "array"
+},
 "images": {
 "description": "A list of images to be pushed upon the successful completion of all build steps. The images will be pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build is marked FAILURE.",
 "items": {
@@ -2772,6 +2779,37 @@
 },
 "type": "object"
 },
+"ContaineranalysisGoogleDevtoolsCloudbuildV1ArtifactsGoModule": {
+"description": "Go module to upload to Artifact Registry upon successful completion of all build steps. A module refers to all dependencies in a go.mod file.",
+"id": "ContaineranalysisGoogleDevtoolsCloudbuildV1ArtifactsGoModule",
+"properties": {
+"modulePath": {
+"description": "Optional. The Go module's \"module path\". e.g. example.com/foo/v2",
+"type": "string"
+},
+"moduleVersion": {
+"description": "Optional. The Go module's semantic version in the form vX.Y.Z. e.g. v0.1.1 Pre-release identifiers can also be added by appending a dash and dot separated ASCII alphanumeric characters and hyphens. e.g. v0.2.3-alpha.x.12m.5",
+"type": "string"
+},
+"repositoryLocation": {
+"description": "Optional. Location of the Artifact Registry repository. i.e. us-east1 Defaults to the build\u2019s location.",
+"type": "string"
+},
+"repositoryName": {
+"description": "Optional. Artifact Registry repository name. Specified Go modules will be zipped and uploaded to Artifact Registry with this location as a prefix. e.g. my-go-repo",
+"type": "string"
+},
+"repositoryProjectId": {
+"description": "Optional. Project ID of the Artifact Registry repository. Defaults to the build project.",
+"type": "string"
+},
+"sourcePath": {
+"description": "Optional. Source path of the go.mod file in the build's workspace. If not specified, this will default to the current directory. e.g. ~/code/go/mypackage",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ContaineranalysisGoogleDevtoolsCloudbuildV1ArtifactsMavenArtifact": {
 "description": "A Maven artifact to upload to Artifact Registry upon successful completion of all build steps.",
 "id": "ContaineranalysisGoogleDevtoolsCloudbuildV1ArtifactsMavenArtifact",
@@ -2860,6 +2898,13 @@
 "readOnly": true,
 "type": "string"
 },
+"dependencies": {
+"description": "Optional. Dependencies that the Cloud Build worker will fetch before executing user steps.",
+"items": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1Dependency"
+},
+"type": "array"
+},
 "failureInfo": {
 "$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1BuildFailureInfo",
 "description": "Output only. Contains information about the build when status=FAILURE.",
@@ -3125,6 +3170,10 @@
 "description": "Option to specify whether or not to apply bash style string operations to the substitutions. NOTE: this is always enabled for triggered builds and cannot be overridden in the build configuration file.",
 "type": "boolean"
 },
+"enableStructuredLogging": {
+"description": "Optional. Option to specify whether structured logging is enabled. If true, JSON-formatted logs are parsed as structured logs.",
+"type": "boolean"
+},
 "env": {
 "description": "A list of global environment variable definitions that will exist for all build steps in this build. If a variable is defined in both globally and in a build step, the variable will use the build step value. The elements are of the form \"KEY=VALUE\" for the environment variable \"KEY\" being given the value \"VALUE\".",
 "items": {
@@ -3206,6 +3255,10 @@ false
 "$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1BuildOptionsPoolOption",
 "description": "Optional. Specification for execution on a `WorkerPool`. See [running builds in a private pool](https://cloud.google.com/build/docs/private-pools/run-builds-in-private-pool) for more information."
 },
+"pubsubTopic": {
+"description": "Optional. Option to specify the Pub/Sub topic to receive build status updates.",
+"type": "string"
+},
 "requestedVerifyOption": {
 "description": "Requested verifiability options.",
 "enum": [
@@ -3232,12 +3285,14 @@ false
 "NONE",
 "SHA256",
 "MD5",
+"GO_MODULE_H1",
 "SHA512"
 ],
 "enumDescriptions": [
 "No hash requested.",
 "Use a sha256 hash.",
 "Use a md5 hash.",
+"Dirhash of a Go module's source code which is then hex-encoded.",
 "Use a sha512 hash."
 ],
 "type": "string"
@@ -3476,6 +3531,64 @@ false
 },
 "type": "object"
 },
+"ContaineranalysisGoogleDevtoolsCloudbuildV1Dependency": {
+"description": "A dependency that the Cloud Build worker will fetch before executing user steps.",
+"id": "ContaineranalysisGoogleDevtoolsCloudbuildV1Dependency",
+"properties": {
+"empty": {
+"description": "If set to true disable all dependency fetching (ignoring the default source as well).",
+"type": "boolean"
+},
+"gitSource": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1DependencyGitSourceDependency",
+"description": "Represents a git repository as a build dependency."
+}
+},
+"type": "object"
+},
+"ContaineranalysisGoogleDevtoolsCloudbuildV1DependencyGitSourceDependency": {
+"description": "Represents a git repository as a build dependency.",
+"id": "ContaineranalysisGoogleDevtoolsCloudbuildV1DependencyGitSourceDependency",
+"properties": {
+"depth": {
+"description": "Optional. How much history should be fetched for the build (default 1, -1 for all history).",
+"format": "int64",
+"type": "string"
+},
+"destPath": {
+"description": "Required. Where should the files be placed on the worker.",
+"type": "string"
+},
+"recurseSubmodules": {
+"description": "Optional. True if submodules should be fetched too (default false).",
+"type": "boolean"
+},
+"repository": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1DependencyGitSourceRepository",
+"description": "Required. The kind of repo (url or dev connect)."
+},
+"revision": {
+"description": "Required. The revision that we will fetch the repo at.",
+"type": "string"
+}
+},
+"type": "object"
+},
+"ContaineranalysisGoogleDevtoolsCloudbuildV1DependencyGitSourceRepository": {
+"description": "A repository for a git source.",
+"id": "ContaineranalysisGoogleDevtoolsCloudbuildV1DependencyGitSourceRepository",
+"properties": {
+"developerConnect": {
+"description": "The Developer Connect Git repository link or the url that matches a repository link in the current project, formatted as `projects/*/locations/*/connections/*/gitRepositoryLink/*`",
+"type": "string"
+},
+"url": {
+"description": "Location of the Git repository.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ContaineranalysisGoogleDevtoolsCloudbuildV1DeveloperConnectConfig": {
 "description": "This config defines the location of a source through Developer Connect.",
 "id": "ContaineranalysisGoogleDevtoolsCloudbuildV1DeveloperConnectConfig",
@@ -3560,12 +3673,14 @@ false
 "NONE",
 "SHA256",
 "MD5",
+"GO_MODULE_H1",
 "SHA512"
 ],
 "enumDescriptions": [
 "No hash requested.",
 "Use a sha256 hash.",
 "Use a md5 hash.",
+"Dirhash of a Go module's source code which is then hex-encoded.",
 "Use a sha512 hash."
 ],
 "type": "string"
@@ -3666,6 +3781,13 @@ false
 },
 "type": "array"
 },
+"goModules": {
+"description": "Optional. Go module artifacts uploaded to Artifact Registry at the end of the build.",
+"items": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1UploadedGoModule"
+},
+"type": "array"
+},
 "images": {
 "description": "Container images that were built as a part of the build.",
 "items": {
@@ -3896,6 +4018,26 @@ false
 },
 "type": "object"
 },
+"ContaineranalysisGoogleDevtoolsCloudbuildV1UploadedGoModule": {
+"description": "A Go module artifact uploaded to Artifact Registry using the GoModule directive.",
+"id": "ContaineranalysisGoogleDevtoolsCloudbuildV1UploadedGoModule",
+"properties": {
+"fileHashes": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1FileHashes",
+"description": "Hash types and values of the Go Module Artifact."
+},
+"pushTiming": {
+"$ref": "ContaineranalysisGoogleDevtoolsCloudbuildV1TimeSpan",
+"description": "Output only. Stores timing information for pushing the specified artifact.",
+"readOnly": true
+},
+"uri": {
+"description": "URI of the uploaded artifact.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ContaineranalysisGoogleDevtoolsCloudbuildV1UploadedMavenArtifact": {
 "description": "A Maven artifact uploaded using the MavenArtifact directive.",
 "id": "ContaineranalysisGoogleDevtoolsCloudbuildV1UploadedMavenArtifact",

googleapiclient/discovery_cache/documents/content.v2.1.json

@@ -4570,7 +4570,7 @@
 }
 }
 },
-"revision": "20250115",
+"revision": "20250208",
 "rootUrl": "https://shoppingcontent.googleapis.com/",
 "schemas": {
 "Account": {
@@ -4944,6 +4944,10 @@ false
 "description": "Details of the issue as a pre-rendered HTML. HTML elements contain CSS classes that can be used to customize the style of the content. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `issue-detail` - top level container for the detail of the issue * `callout-banners` - section of the `issue-detail` with callout banners * `callout-banner` - single callout banner, inside `callout-banners` * `callout-banner-info` - callout with important information (default) * `callout-banner-warning` - callout with a warning * `callout-banner-error` - callout informing about an error (most severe) * `issue-content` - section of the `issue-detail`, contains multiple `content-element` * `content-element` - content element such as a list, link or paragraph, inside `issue-content` * `root-causes` - unordered list with items describing root causes of the issue, inside `issue-content` * `root-causes-intro` - intro text before the `root-causes` list, inside `issue-content` * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon. * `content-moderation` - marks the paragraph that explains how the issue was identified. * `new-element` - Present for new elements added to the pre-rendered content in the future. To make sure that a new content element does not break your style, you can hide everything with this class.",
 "type": "string"
 },
+"prerenderedOutOfCourtDisputeSettlement": {
+"description": "Pre-rendered HTML that contains a link to the external location where the ODS can be requested and instructions for how to request it. HTML elements contain CSS classes that can be used to customize the style of this snippet. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `ods-section`* - wrapper around the out-of-court dispute resolution section * `ods-description`* - intro text for the out-of-court dispute resolution. It may contain multiple segments and a link. * `ods-param`* - wrapper around the header-value pair for parameters that merchant may need to provide during the ODS process. * `ods-routing-id`* - ods param for the Routing ID. * `ods-reference-id`* - ods param for the Routing ID. * `ods-param-header`* - header for the ODS parameter * `ods-param-value`* - value of the ODS parameter. This value should be rendered in a way that it is easy for merchants to identify and copy. * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon.",
+"type": "string"
+},
 "title": {
 "description": "Title of the issue.",
 "type": "string"
@@ -10758,6 +10762,10 @@ false
 "description": "Details of the issue as a pre-rendered HTML. HTML elements contain CSS classes that can be used to customize the style of the content. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `issue-detail` - top level container for the detail of the issue * `callout-banners` - section of the `issue-detail` with callout banners * `callout-banner` - single callout banner, inside `callout-banners` * `callout-banner-info` - callout with important information (default) * `callout-banner-warning` - callout with a warning * `callout-banner-error` - callout informing about an error (most severe) * `issue-content` - section of the `issue-detail`, contains multiple `content-element` * `content-element` - content element such as a list, link or paragraph, inside `issue-content` * `root-causes` - unordered list with items describing root causes of the issue, inside `issue-content` * `root-causes-intro` - intro text before the `root-causes` list, inside `issue-content` * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon. * `content-moderation` - marks the paragraph that explains how the issue was identified. * `list-intro` - marks the paragraph that contains an intro for a list. This paragraph will be always followed by a list. * `new-element` - Present for new elements added to the pre-rendered content in the future. To make sure that a new content element does not break your style, you can hide everything with this class.",
 "type": "string"
 },
+"prerenderedOutOfCourtDisputeSettlement": {
+"description": "Pre-rendered HTML that contains a link to the external location where the ODS can be requested and instructions for how to request it. HTML elements contain CSS classes that can be used to customize the style of this snippet. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `ods-section`* - wrapper around the out-of-court dispute resolution section * `ods-description`* - intro text for the out-of-court dispute resolution. It may contain multiple segments and a link. * `ods-param`* - wrapper around the header-value pair for parameters that merchant may need to provide during the ODS process. * `ods-routing-id`* - ods param for the Routing ID. * `ods-reference-id`* - ods param for the Routing ID. * `ods-param-header`* - header for the ODS parameter * `ods-param-value`* - value of the ODS parameter. This value should be rendered in a way that it is easy for merchants to identify and copy. * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon.",
+"type": "string"
+},
 "title": {
 "description": "Title of the issue.",
 "type": "string"
@@ -12492,7 +12500,8 @@ false
 "properties": {
 "alternateDisputeResolution": {
 "$ref": "AlternateDisputeResolution",
-"description": "The Alternate Dispute Resolution (ADR) contains a link to a page where merchant can bring their appeal to an [external body](https://support.google.com/european-union-digital-services-act-redress-options/answer/13535501). If the ADR is present, it MUST be available to the merchant on the page that shows the list with their account issues."
+"deprecated": true,
+"description": "Alternate Dispute Resolution (ADR) is deprecated. Use `prerendered_out_of_court_dispute_settlement` instead."
 },
 "issues": {
 "description": "List of account issues for a given account. This list can be shown with compressed, expandable items. In the compressed form, the title and impact should be shown for each issue. Once the issue is expanded, the detailed content and available actions should be rendered.",
@@ -12543,7 +12552,8 @@ false
 "properties": {
 "alternateDisputeResolution": {
 "$ref": "AlternateDisputeResolution",
-"description": "The Alternate Dispute Resolution (ADR) contains a link to a page where merchant can bring their appeal to an [external body](https://support.google.com/european-union-digital-services-act-redress-options/answer/13535501). If present, the link should be shown on the same page as the list of issues."
+"deprecated": true,
+"description": "Alternate Dispute Resolution (ADR) is deprecated. Use `prerendered_out_of_court_dispute_settlement` instead."
 },
 "issues": {
 "description": "List of issues for a given product. This list can be shown with compressed, expandable items. In the compressed form, the title and impact should be shown for each issue. Once the issue is expanded, the detailed content and available actions should be rendered.",

googleapiclient/discovery_cache/documents/css.v1.json

@@ -226,7 +226,7 @@
 ],
 "parameters": {
 "name": {
-"description": "Required. The name of the CSS product input resource to delete. Format: accounts/{account}/cssProductInputs/{css_product_input}",
+"description": "Required. The name of the CSS product input resource to delete. Format: accounts/{account}/cssProductInputs/{css_product_input}, where the last section `css_product_input` consists of 3 parts: contentLanguage~feedLabel~offerId. Example: accounts/123/cssProductInputs/de~DE~rawProvidedId123",
 "location": "path",
 "pattern": "^accounts/[^/]+/cssProductInputs/[^/]+$",
 "required": true,
@@ -292,7 +292,7 @@
 ],
 "parameters": {
 "name": {
-"description": "The name of the CSS Product input. Format: `accounts/{account}/cssProductInputs/{css_product_input}`",
+"description": "The name of the CSS Product input. Format: `accounts/{account}/cssProductInputs/{css_product_input}`, where the last section `css_product_input` consists of 3 parts: contentLanguage~feedLabel~offerId. Example: accounts/123/cssProductInputs/de~DE~rawProvidedId123",
 "location": "path",
 "pattern": "^accounts/[^/]+/cssProductInputs/[^/]+$",
 "required": true,
@@ -507,7 +507,7 @@
 }
 }
 },
-"revision": "20250106",
+"revision": "20250219",
 "rootUrl": "https://css.googleapis.com/",
 "schemas": {
 "Account": {
@@ -576,7 +576,7 @@
 "type": "string"
 },
 "parent": {
-"description": "The CSS/MC account's parent resource. CSS group for CSS domains; CSS domain for MC accounts. Returned only if the user has access to the parent account.",
+"description": "The CSS/MC account's parent resource. CSS group for CSS domains; CSS domain for MC accounts. Returned only if the user has access to the parent account. Note: For MC sub-accounts, this is also the CSS domain that is the parent resource of the MCA account, since we are effectively flattening the hierarchy.\"",
 "type": "string"
 }
 },
@@ -960,7 +960,7 @@
 "type": "string"
 },
 "name": {
-"description": "The name of the CSS Product input. Format: `accounts/{account}/cssProductInputs/{css_product_input}`",
+"description": "The name of the CSS Product input. Format: `accounts/{account}/cssProductInputs/{css_product_input}`, where the last section `css_product_input` consists of 3 parts: contentLanguage~feedLabel~offerId. Example: accounts/123/cssProductInputs/de~DE~rawProvidedId123",
 "type": "string"
 },
 "rawProvidedId": {