google-api-python-client 2.97.0__py2.py3-none-any.whl → 2.99.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/chromepolicy.v1.json

@@ -557,7 +557,7 @@
       }
     }
   },
-  "revision": "20230813",
+  "revision": "20230910",
   "rootUrl": "https://chromepolicy.googleapis.com/",
   "schemas": {
     "ChromeCrosDpanelAutosettingsProtoPolicyApiLifecycle": {
@@ -1678,6 +1678,28 @@
       "description": "Describes a complete .proto file.",
       "id": "Proto2FileDescriptorProto",
       "properties": {
+        "editionEnum": {
+          "description": "The edition of the proto file.",
+          "enum": [
+            "EDITION_UNKNOWN",
+            "EDITION_2023",
+            "EDITION_1_TEST_ONLY",
+            "EDITION_2_TEST_ONLY",
+            "EDITION_99997_TEST_ONLY",
+            "EDITION_99998_TEST_ONLY",
+            "EDITION_99999_TEST_ONLY"
+          ],
+          "enumDescriptions": [
+            "A placeholder for an unknown edition value.",
+            "Editions that have been released. The specific values are arbitrary and should not be depended on, but they will always be time-ordered for easy comparison.",
+            "Placeholder editions for testing feature resolution. These should not be used or relyed on outside of tests.",
+            "",
+            "",
+            "",
+            ""
+          ],
+          "type": "string"
+        },
         "enumType": {
           "items": {
             "$ref": "Proto2EnumDescriptorProto"

googleapiclient/discovery_cache/documents/chromeuxreport.v1.json

@@ -131,7 +131,7 @@
       }
     }
   },
-  "revision": "20230808",
+  "revision": "20230905",
   "rootUrl": "https://chromeuxreport.googleapis.com/",
   "schemas": {
     "Bin": {

googleapiclient/discovery_cache/documents/civicinfo.v2.json

@@ -365,7 +365,7 @@
       }
     }
   },
-  "revision": "20230808",
+  "revision": "20230908",
   "rootUrl": "https://civicinfo.googleapis.com/",
   "schemas": {
     "AdministrationRegion": {

googleapiclient/discovery_cache/documents/classroom.v1.json

@@ -2400,7 +2400,7 @@
       }
     }
   },
-  "revision": "20230808",
+  "revision": "20230905",
   "rootUrl": "https://classroom.googleapis.com/",
   "schemas": {
     "Announcement": {

googleapiclient/discovery_cache/documents/cloudasset.v1.json

@@ -1095,7 +1095,7 @@
       }
     }
   },
-  "revision": "20230805",
+  "revision": "20230902",
   "rootUrl": "https://cloudasset.googleapis.com/",
   "schemas": {
     "AccessSelector": {
@@ -2552,7 +2552,7 @@
           "type": "string"
         },
         "scopes": {
-          "description": "The scopes of a policy define which resources an ACM policy can restrict, and where ACM resources can be referenced. For example, a policy with scopes=[\"folders/123\"] has the following behavior: - vpcsc perimeters can only restrict projects within folders/123 - access levels can only be referenced by resources within folders/123. If empty, there are no limitations on which resources can be restricted by an ACM policy, and there are no limitations on where ACM resources can be referenced. Only one policy can include a given scope (attempting to create a second policy which includes \"folders/123\" will result in an error). Currently, scopes cannot be modified after a policy is created. Currently, policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
+          "description": "The scopes of the AccessPolicy. Scopes define which resources a policy can restrict and where its resources can be referenced. For example, policy A with `scopes=[\"folders/123\"]` has the following behavior: - ServicePerimeter can only restrict projects within `folders/123`. - ServicePerimeter within policy A can only reference access levels defined within policy A. - Only one policy can include a given scope; thus, attempting to create a second policy which includes `folders/123` will result in an error. If no scopes are provided, then any resource within the organization can be restricted. Scopes cannot be modified after a policy is created. Policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
           "items": {
             "type": "string"
           },
@@ -4032,6 +4032,13 @@
           "description": "A map of related resources of this resource, keyed by the relationship type. A relationship type is in the format of {SourceType}_{ACTION}_{DestType}. Example: `DISK_TO_INSTANCE`, `DISK_TO_NETWORK`, `INSTANCE_TO_INSTANCEGROUP`. See [supported relationship types](https://cloud.google.com/asset-inventory/docs/supported-asset-types#supported_relationship_types).",
           "type": "object"
         },
+        "sccSecurityMarks": {
+          "additionalProperties": {
+            "type": "string"
+          },
+          "description": "The actual content of Security Command Center security marks associated with the asset. Note that both staging & prod SecurityMarks are attached on prod resources. In CAS preprod/prod, both staging & prod SecurityMarks are ingested and returned in the following `security_marks` map. In that case, the prefix \"staging.\" will be added to the keys of all the staging marks. To search against SCC SecurityMarks field: * Use a field query: - query by a given key value pair. Example: `sccSecurityMarks.foo=bar` - query by a given key's existence. Example: `sccSecurityMarks.foo:*`",
+          "type": "object"
+        },
         "state": {
           "description": "The state of this resource. Different resources types have different state definitions that are mapped from various fields of different resource types. This field is available only when the resource's Protobuf contains it. Example: If the resource is an instance provided by Compute Engine, its state will include PROVISIONING, STAGING, RUNNING, STOPPING, SUSPENDING, SUSPENDED, REPAIRING, and TERMINATED. See `status` definition in [API Reference](https://cloud.google.com/compute/docs/reference/rest/v1/instances). If the resource is a project provided by Resource Manager, its state will include LIFECYCLE_STATE_UNSPECIFIED, ACTIVE, DELETE_REQUESTED and DELETE_IN_PROGRESS. See `lifecycleState` definition in [API Reference](https://cloud.google.com/resource-manager/reference/rest/v1/projects). To search against the `state`: * Use a field query. Example: `state:RUNNING` * Use a free text query. Example: `RUNNING`",
           "type": "string"

googleapiclient/discovery_cache/documents/cloudasset.v1beta1.json

@@ -411,7 +411,7 @@
       }
     }
   },
-  "revision": "20230805",
+  "revision": "20230902",
   "rootUrl": "https://cloudasset.googleapis.com/",
   "schemas": {
     "AnalyzeIamPolicyLongrunningMetadata": {
@@ -936,7 +936,7 @@
           "type": "string"
         },
         "scopes": {
-          "description": "The scopes of a policy define which resources an ACM policy can restrict, and where ACM resources can be referenced. For example, a policy with scopes=[\"folders/123\"] has the following behavior: - vpcsc perimeters can only restrict projects within folders/123 - access levels can only be referenced by resources within folders/123. If empty, there are no limitations on which resources can be restricted by an ACM policy, and there are no limitations on where ACM resources can be referenced. Only one policy can include a given scope (attempting to create a second policy which includes \"folders/123\" will result in an error). Currently, scopes cannot be modified after a policy is created. Currently, policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
+          "description": "The scopes of the AccessPolicy. Scopes define which resources a policy can restrict and where its resources can be referenced. For example, policy A with `scopes=[\"folders/123\"]` has the following behavior: - ServicePerimeter can only restrict projects within `folders/123`. - ServicePerimeter within policy A can only reference access levels defined within policy A. - Only one policy can include a given scope; thus, attempting to create a second policy which includes `folders/123` will result in an error. If no scopes are provided, then any resource within the organization can be restricted. Scopes cannot be modified after a policy is created. Policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
           "items": {
             "type": "string"
           },

googleapiclient/discovery_cache/documents/cloudasset.v1p1beta1.json

@@ -207,7 +207,7 @@
       }
     }
   },
-  "revision": "20230805",
+  "revision": "20230902",
   "rootUrl": "https://cloudasset.googleapis.com/",
   "schemas": {
     "AnalyzeIamPolicyLongrunningMetadata": {
@@ -638,7 +638,7 @@
           "type": "string"
         },
         "scopes": {
-          "description": "The scopes of a policy define which resources an ACM policy can restrict, and where ACM resources can be referenced. For example, a policy with scopes=[\"folders/123\"] has the following behavior: - vpcsc perimeters can only restrict projects within folders/123 - access levels can only be referenced by resources within folders/123. If empty, there are no limitations on which resources can be restricted by an ACM policy, and there are no limitations on where ACM resources can be referenced. Only one policy can include a given scope (attempting to create a second policy which includes \"folders/123\" will result in an error). Currently, scopes cannot be modified after a policy is created. Currently, policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
+          "description": "The scopes of the AccessPolicy. Scopes define which resources a policy can restrict and where its resources can be referenced. For example, policy A with `scopes=[\"folders/123\"]` has the following behavior: - ServicePerimeter can only restrict projects within `folders/123`. - ServicePerimeter within policy A can only reference access levels defined within policy A. - Only one policy can include a given scope; thus, attempting to create a second policy which includes `folders/123` will result in an error. If no scopes are provided, then any resource within the organization can be restricted. Scopes cannot be modified after a policy is created. Policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
           "items": {
             "type": "string"
           },

googleapiclient/discovery_cache/documents/cloudasset.v1p5beta1.json

@@ -177,7 +177,7 @@
       }
     }
   },
-  "revision": "20230811",
+  "revision": "20230902",
   "rootUrl": "https://cloudasset.googleapis.com/",
   "schemas": {
     "AnalyzeIamPolicyLongrunningMetadata": {
@@ -643,7 +643,7 @@
           "type": "string"
         },
         "scopes": {
-          "description": "The scopes of a policy define which resources an ACM policy can restrict, and where ACM resources can be referenced. For example, a policy with scopes=[\"folders/123\"] has the following behavior: - vpcsc perimeters can only restrict projects within folders/123 - access levels can only be referenced by resources within folders/123. If empty, there are no limitations on which resources can be restricted by an ACM policy, and there are no limitations on where ACM resources can be referenced. Only one policy can include a given scope (attempting to create a second policy which includes \"folders/123\" will result in an error). Currently, scopes cannot be modified after a policy is created. Currently, policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
+          "description": "The scopes of the AccessPolicy. Scopes define which resources a policy can restrict and where its resources can be referenced. For example, policy A with `scopes=[\"folders/123\"]` has the following behavior: - ServicePerimeter can only restrict projects within `folders/123`. - ServicePerimeter within policy A can only reference access levels defined within policy A. - Only one policy can include a given scope; thus, attempting to create a second policy which includes `folders/123` will result in an error. If no scopes are provided, then any resource within the organization can be restricted. Scopes cannot be modified after a policy is created. Policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
           "items": {
             "type": "string"
           },

googleapiclient/discovery_cache/documents/cloudasset.v1p7beta1.json

@@ -167,7 +167,7 @@
       }
     }
   },
-  "revision": "20230805",
+  "revision": "20230902",
   "rootUrl": "https://cloudasset.googleapis.com/",
   "schemas": {
     "AnalyzeIamPolicyLongrunningMetadata": {
@@ -712,7 +712,7 @@
           "type": "string"
         },
         "scopes": {
-          "description": "The scopes of a policy define which resources an ACM policy can restrict, and where ACM resources can be referenced. For example, a policy with scopes=[\"folders/123\"] has the following behavior: - vpcsc perimeters can only restrict projects within folders/123 - access levels can only be referenced by resources within folders/123. If empty, there are no limitations on which resources can be restricted by an ACM policy, and there are no limitations on where ACM resources can be referenced. Only one policy can include a given scope (attempting to create a second policy which includes \"folders/123\" will result in an error). Currently, scopes cannot be modified after a policy is created. Currently, policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
+          "description": "The scopes of the AccessPolicy. Scopes define which resources a policy can restrict and where its resources can be referenced. For example, policy A with `scopes=[\"folders/123\"]` has the following behavior: - ServicePerimeter can only restrict projects within `folders/123`. - ServicePerimeter within policy A can only reference access levels defined within policy A. - Only one policy can include a given scope; thus, attempting to create a second policy which includes `folders/123` will result in an error. If no scopes are provided, then any resource within the organization can be restricted. Scopes cannot be modified after a policy is created. Policies can only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`",
           "items": {
             "type": "string"
           },

googleapiclient/discovery_cache/documents/cloudbilling.v1.json

@@ -114,7 +114,7 @@
     "billingAccounts": {
       "methods": {
         "create": {
-          "description": "This method creates [billing subaccounts](https://cloud.google.com/billing/docs/concepts#subaccounts). Google Cloud resellers should use the Channel Services APIs, [accounts.customers.create](https://cloud.google.com/channel/docs/reference/rest/v1/accounts.customers/create) and [accounts.customers.entitlements.create](https://cloud.google.com/channel/docs/reference/rest/v1/accounts.customers.entitlements/create). When creating a subaccount, the current authenticated user must have the `billing.accounts.update` IAM permission on the parent account, which is typically given to billing account [administrators](https://cloud.google.com/billing/docs/how-to/billing-access). This method will return an error if the parent account has not been provisioned as a reseller account.",
+          "description": "This method creates [billing subaccounts](https://cloud.google.com/billing/docs/concepts#subaccounts). Google Cloud resellers should use the Channel Services APIs, [accounts.customers.create](https://cloud.google.com/channel/docs/reference/rest/v1/accounts.customers/create) and [accounts.customers.entitlements.create](https://cloud.google.com/channel/docs/reference/rest/v1/accounts.customers.entitlements/create). When creating a subaccount, the current authenticated user must have the `billing.accounts.update` IAM permission on the parent account, which is typically given to billing account [administrators](https://cloud.google.com/billing/docs/how-to/billing-access). This method will return an error if the parent account has not been provisioned for subaccounts.",
           "flatPath": "v1/billingAccounts",
           "httpMethod": "POST",
           "id": "cloudbilling.billingAccounts.create",
@@ -200,7 +200,7 @@
           "parameterOrder": [],
           "parameters": {
             "filter": {
-              "description": "Options for how to filter the returned billing accounts. Currently this only supports filtering for [subaccounts](https://cloud.google.com/billing/docs/concepts) under a single provided reseller billing account. (e.g. \"master_billing_account=billingAccounts/012345-678901-ABCDEF\"). Boolean algebra and other fields are not currently supported.",
+              "description": "Options for how to filter the returned billing accounts. This only supports filtering for [subaccounts](https://cloud.google.com/billing/docs/concepts) under a single provided parent billing account. (e.g. \"master_billing_account=billingAccounts/012345-678901-ABCDEF\"). Boolean algebra and other fields are not currently supported.",
               "location": "query",
               "type": "string"
             },
@@ -521,7 +521,7 @@
       }
     }
   },
-  "revision": "20230803",
+  "revision": "20230901",
   "rootUrl": "https://cloudbilling.googleapis.com/",
   "schemas": {
     "AggregationInfo": {

googleapiclient/discovery_cache/documents/cloudbilling.v1beta.json

@@ -664,7 +664,7 @@
       }
     }
   },
-  "revision": "20230811",
+  "revision": "20230901",
   "rootUrl": "https://cloudbilling.googleapis.com/",
   "schemas": {
     "CacheFillRegions": {
@@ -1302,7 +1302,7 @@
           "description": "Percentage of the fixed discount."
         },
         "discountScopeType": {
-          "description": "Type of the fixed discount scope which indicates the source of the discount. It can have values such as 'sku-group'.",
+          "description": "Type of the fixed discount scope which indicates the source of the discount. It can have values such as 'unspecified' and 'sku-group'.",
           "type": "string"
         },
         "fixTime": {
@@ -1332,7 +1332,7 @@
           "description": "Percentage of the floating discount."
         },
         "discountScopeType": {
-          "description": "Type of the floating discount scope which indicates the source of the discount. It can have values such as 'sku-group'.",
+          "description": "Type of the floating discount scope which indicates the source of the discount. It can have values such as 'unspecified' and 'sku-group'.",
           "type": "string"
         },
         "skuGroup": {
@@ -1358,16 +1358,8 @@
       "description": "Encapsulates a price migrated from other SKUs.",
       "id": "GoogleCloudBillingBillingaccountpricesV1betaMigratedPrice",
       "properties": {
-        "sourceDiscountOnTargetPrice": {
-          "$ref": "GoogleCloudBillingBillingaccountpricesV1betaSourceDiscountOnTargetPrice",
-          "description": "The source SKU floating discount is applied on the target SKU's default price."
-        },
         "sourceSku": {
-          "description": "Source SKU where the discount is migrated from.",
-          "type": "string"
-        },
-        "type": {
-          "description": "Type of the migrated price. It can have values such as 'source-discount-on-target-price'.",
+          "description": "Source SKU where the discount is migrated from. Format: billingAccounts/{billing_account}/skus/{sku}",
           "type": "string"
         }
       },
@@ -1406,7 +1398,7 @@
           "description": "Price migrated from other SKUs."
         },
         "type": {
-          "description": "Type of the price reason. It can values such as 'default-price', 'fixed-price', 'fixed-discount', 'floating-discount', 'migrated-price', 'merged-price', 'list-price-as-ceiling'.",
+          "description": "Type of the price reason. It can have values such as 'unspecified', 'default-price', 'fixed-price', 'fixed-discount', 'floating-discount', 'migrated-price', 'merged-price', 'list-price-as-ceiling'.",
           "type": "string"
         }
       },
@@ -1457,17 +1449,6 @@
       },
       "type": "object"
     },
-    "GoogleCloudBillingBillingaccountpricesV1betaSourceDiscountOnTargetPrice": {
-      "description": "Encapsulates a type of MigratedPrice where the source SKU floating discount is applied on the target SKU's default price.",
-      "id": "GoogleCloudBillingBillingaccountpricesV1betaSourceDiscountOnTargetPrice",
-      "properties": {
-        "migratedDiscountPercent": {
-          "$ref": "Decimal",
-          "description": "Discount percent of the source SKU that is applied on the target SKU's default price."
-        }
-      },
-      "type": "object"
-    },
     "GoogleCloudBillingBillingaccountpricesV1betaUnitInfo": {
       "description": "Encapsulates the unit information for a Rate",
       "id": "GoogleCloudBillingBillingaccountpricesV1betaUnitInfo",

googleapiclient/discovery_cache/documents/cloudbuild.v1.json

@@ -1582,7 +1582,7 @@
             "triggers": {
               "methods": {
                 "create": {
-                  "description": "Creates a new `BuildTrigger`. This API is experimental.",
+                  "description": "Creates a new `BuildTrigger`.",
                   "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/triggers",
                   "httpMethod": "POST",
                   "id": "cloudbuild.projects.locations.triggers.create",
@@ -1615,7 +1615,7 @@
                   ]
                 },
                 "delete": {
-                  "description": "Deletes a `BuildTrigger` by its project ID and trigger ID. This API is experimental.",
+                  "description": "Deletes a `BuildTrigger` by its project ID and trigger ID.",
                   "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/triggers/{triggersId}",
                   "httpMethod": "DELETE",
                   "id": "cloudbuild.projects.locations.triggers.delete",
@@ -1650,7 +1650,7 @@
                   ]
                 },
                 "get": {
-                  "description": "Returns information about a `BuildTrigger`. This API is experimental.",
+                  "description": "Returns information about a `BuildTrigger`.",
                   "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/triggers/{triggersId}",
                   "httpMethod": "GET",
                   "id": "cloudbuild.projects.locations.triggers.get",
@@ -1685,7 +1685,7 @@
                   ]
                 },
                 "list": {
-                  "description": "Lists existing `BuildTrigger`s. This API is experimental.",
+                  "description": "Lists existing `BuildTrigger`s.",
                   "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/triggers",
                   "httpMethod": "GET",
                   "id": "cloudbuild.projects.locations.triggers.list",
@@ -1726,7 +1726,7 @@
                   ]
                 },
                 "patch": {
-                  "description": "Updates a `BuildTrigger` by its project ID and trigger ID. This API is experimental.",
+                  "description": "Updates a `BuildTrigger` by its project ID and trigger ID.",
                   "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/triggers/{triggersId}",
                   "httpMethod": "PATCH",
                   "id": "cloudbuild.projects.locations.triggers.patch",
@@ -2026,7 +2026,7 @@
         "triggers": {
           "methods": {
             "create": {
-              "description": "Creates a new `BuildTrigger`. This API is experimental.",
+              "description": "Creates a new `BuildTrigger`.",
               "flatPath": "v1/projects/{projectId}/triggers",
               "httpMethod": "POST",
               "id": "cloudbuild.projects.triggers.create",
@@ -2058,7 +2058,7 @@
               ]
             },
             "delete": {
-              "description": "Deletes a `BuildTrigger` by its project ID and trigger ID. This API is experimental.",
+              "description": "Deletes a `BuildTrigger` by its project ID and trigger ID.",
               "flatPath": "v1/projects/{projectId}/triggers/{triggerId}",
               "httpMethod": "DELETE",
               "id": "cloudbuild.projects.triggers.delete",
@@ -2094,7 +2094,7 @@
               ]
             },
             "get": {
-              "description": "Returns information about a `BuildTrigger`. This API is experimental.",
+              "description": "Returns information about a `BuildTrigger`.",
               "flatPath": "v1/projects/{projectId}/triggers/{triggerId}",
               "httpMethod": "GET",
               "id": "cloudbuild.projects.triggers.get",
@@ -2130,7 +2130,7 @@
               ]
             },
             "list": {
-              "description": "Lists existing `BuildTrigger`s. This API is experimental.",
+              "description": "Lists existing `BuildTrigger`s.",
               "flatPath": "v1/projects/{projectId}/triggers",
               "httpMethod": "GET",
               "id": "cloudbuild.projects.triggers.list",
@@ -2170,7 +2170,7 @@
               ]
             },
             "patch": {
-              "description": "Updates a `BuildTrigger` by its project ID and trigger ID. This API is experimental.",
+              "description": "Updates a `BuildTrigger` by its project ID and trigger ID.",
               "flatPath": "v1/projects/{projectId}/triggers/{triggerId}",
               "httpMethod": "PATCH",
               "id": "cloudbuild.projects.triggers.patch",
@@ -2319,7 +2319,7 @@
       }
     }
   },
-  "revision": "20230811",
+  "revision": "20230907",
   "rootUrl": "https://cloudbuild.googleapis.com/",
   "schemas": {
     "ApprovalConfig": {
@@ -4783,7 +4783,7 @@
           "type": "array"
         },
         "buildStepOutputs": {
-          "description": "List of build step outputs, produced by builder images, in the order corresponding to build step indices. [Cloud Builders](https://cloud.google.com/cloud-build/docs/cloud-builders) can produce this output by writing to `$BUILDER_OUTPUT/output`. Only the first 4KB of data is stored.",
+          "description": "List of build step outputs, produced by builder images, in the order corresponding to build step indices. [Cloud Builders](https://cloud.google.com/cloud-build/docs/cloud-builders) can produce this output by writing to `$BUILDER_OUTPUT/output`. Only the first 50KB of data is stored.",
           "items": {
             "format": "byte",
             "type": "string"