Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(all): auto-regenerate discovery clients #1928

Merged
merged 1 commit into from Apr 5, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
16 changes: 15 additions & 1 deletion advisorynotifications/v1/advisorynotifications-api.json
Expand Up @@ -204,7 +204,7 @@
}
}
},
"revision": "20230219",
"revision": "20230402",
"rootUrl": "https://advisorynotifications.googleapis.com/",
"schemas": {
"GoogleCloudAdvisorynotificationsV1Attachment": {
Expand Down Expand Up @@ -340,6 +340,20 @@
"description": "The resource name of the notification. Format: organizations/{organization}/locations/{location}/notifications/{notification}.",
"type": "string"
},
"notificationType": {
"description": "Type of notification",
"enum": [
"NOTIFICATION_TYPE_UNSPECIFIED",
"NOTIFICATION_TYPE_SECURITY_PRIVACY_ADVISORY",
"NOTIFICATION_TYPE_SENSITIVE_ACTIONS"
],
"enumDescriptions": [
"Default type",
"Security and privacy advisory notifications",
"Sensitive action notifications"
],
"type": "string"
},
"subject": {
"$ref": "GoogleCloudAdvisorynotificationsV1Subject",
"description": "The subject line of the notification."
Expand Down
10 changes: 10 additions & 0 deletions advisorynotifications/v1/advisorynotifications-gen.go

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

4 changes: 2 additions & 2 deletions apigee/v1/apigee-api.json
Expand Up @@ -8744,7 +8744,7 @@
}
}
},
"revision": "20230312",
"revision": "20230329",
"rootUrl": "https://apigee.googleapis.com/",
"schemas": {
"EdgeConfigstoreBundleBadBundle": {
Expand Down Expand Up @@ -13189,7 +13189,7 @@
"type": "string"
},
"authorizedNetwork": {
"description": "Name of the customer project's VPC network. If provided, the network needs to be peered through Service Networking. If none is provided, the organization will have access only to the public internet.",
"description": "Compute Engine network used for Service Networking to be peered with Apigee runtime instances. See [Getting started with the Service Networking API](https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started). Apigee also supports shared VPC (that is, the host network project is not the same as the one that is peering with Apigee). See [Shared VPC overview](https://cloud.google.com/vpc/docs/shared-vpc). To use a shared VPC network, use the following format: `projects/{host-project-id}/{region}/networks/{network-name}`. For example: `projects/my-sharedvpc-host/global/networks/mynetwork`",
"type": "string"
},
"runtimeLocation": {
Expand Down
14 changes: 10 additions & 4 deletions apigee/v1/apigee-gen.go

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

6 changes: 5 additions & 1 deletion cloudsupport/v2beta/cloudsupport-api.json
Expand Up @@ -543,7 +543,7 @@
}
}
},
"revision": "20230330",
"revision": "20230404",
"rootUrl": "https://cloudsupport.googleapis.com/",
"schemas": {
"Actor": {
Expand Down Expand Up @@ -642,6 +642,10 @@
"$ref": "CaseClassification",
"description": "The issue classification applicable to this case."
},
"contactEmail": {
"description": "A user-supplied email address to send case update notifications for. This should only be used in BYOID flows, where we cannot infer the user's email address directly from their EUCs.",
"type": "string"
},
"createTime": {
"description": "Output only. The time this case was created.",
"format": "google-datetime",
Expand Down
5 changes: 5 additions & 0 deletions cloudsupport/v2beta/cloudsupport-gen.go

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

22 changes: 21 additions & 1 deletion compute/v0.beta/compute-api.json
Expand Up @@ -36741,7 +36741,7 @@
}
}
},
"revision": "20230322",
"revision": "20230327",
"rootUrl": "https://compute.googleapis.com/",
"schemas": {
"AWSV4Signature": {
Expand Down Expand Up @@ -41994,6 +41994,14 @@
"DiskAsyncReplication": {
"id": "DiskAsyncReplication",
"properties": {
"consistencyGroupPolicy": {
"description": "[Output Only] URL of the DiskConsistencyGroupPolicy if replication was started on the disk as a member of a group.",
"type": "string"
},
"consistencyGroupPolicyId": {
"description": "[Output Only] ID of the DiskConsistencyGroupPolicy if replication was started on the disk as a member of a group.",
"type": "string"
},
"disk": {
"description": "The other disk asynchronously replicated to or from the current disk. You can provide this as a partial or full URL to the resource. For example, the following are valid values: - https://www.googleapis.com/compute/v1/projects/project/zones/zone /disks/disk - projects/project/zones/zone/disks/disk - zones/zone/disks/disk ",
"type": "string"
Expand Down Expand Up @@ -60055,11 +60063,15 @@
"NETWORK_ATTACHMENTS",
"NETWORK_ENDPOINT_GROUPS",
"NETWORK_FIREWALL_POLICIES",
"NET_LB_SECURITY_POLICIES_PER_REGION",
"NET_LB_SECURITY_POLICY_RULES_PER_REGION",
"NET_LB_SECURITY_POLICY_RULE_ATTRIBUTES_PER_REGION",
"NODE_GROUPS",
"NODE_TEMPLATES",
"NVIDIA_A100_80GB_GPUS",
"NVIDIA_A100_GPUS",
"NVIDIA_K80_GPUS",
"NVIDIA_L4_GPUS",
"NVIDIA_P100_GPUS",
"NVIDIA_P100_VWS_GPUS",
"NVIDIA_P4_GPUS",
Expand All @@ -60074,6 +60086,7 @@
"PREEMPTIBLE_NVIDIA_A100_80GB_GPUS",
"PREEMPTIBLE_NVIDIA_A100_GPUS",
"PREEMPTIBLE_NVIDIA_K80_GPUS",
"PREEMPTIBLE_NVIDIA_L4_GPUS",
"PREEMPTIBLE_NVIDIA_P100_GPUS",
"PREEMPTIBLE_NVIDIA_P100_VWS_GPUS",
"PREEMPTIBLE_NVIDIA_P4_GPUS",
Expand All @@ -60098,6 +60111,7 @@
"ROUTES",
"SECURITY_POLICIES",
"SECURITY_POLICIES_PER_REGION",
"SECURITY_POLICY_ADVANCED_RULES_PER_REGION",
"SECURITY_POLICY_CEVAL_RULES",
"SECURITY_POLICY_RULES",
"SECURITY_POLICY_RULES_PER_REGION",
Expand Down Expand Up @@ -60247,6 +60261,12 @@
"",
"",
"",
"",
"",
"",
"",
"",
"",
"The total number of snapshots allowed for a single project.",
"",
"",
Expand Down
42 changes: 30 additions & 12 deletions compute/v0.beta/compute-gen.go
Expand Up @@ -9668,6 +9668,16 @@ func (s *DiskAggregatedListWarningData) MarshalJSON() ([]byte, error) {
}

type DiskAsyncReplication struct {
// ConsistencyGroupPolicy: [Output Only] URL of the
// DiskConsistencyGroupPolicy if replication was started on the disk as
// a member of a group.
ConsistencyGroupPolicy string `json:"consistencyGroupPolicy,omitempty"`

// ConsistencyGroupPolicyId: [Output Only] ID of the
// DiskConsistencyGroupPolicy if replication was started on the disk as
// a member of a group.
ConsistencyGroupPolicyId string `json:"consistencyGroupPolicyId,omitempty"`

// Disk: The other disk asynchronously replicated to or from the current
// disk. You can provide this as a partial or full URL to the resource.
// For example, the following are valid values: -
Expand All @@ -9684,20 +9694,22 @@ type DiskAsyncReplication struct {
// identify the exact version of the disk that was used.
DiskId string `json:"diskId,omitempty"`

// ForceSendFields is a list of field names (e.g. "Disk") to
// unconditionally include in API requests. By default, fields with
// empty or default values are omitted from API requests. However, any
// non-pointer, non-interface field appearing in ForceSendFields will be
// sent to the server regardless of whether the field is empty or not.
// This may be used to include empty fields in Patch requests.
// ForceSendFields is a list of field names (e.g.
// "ConsistencyGroupPolicy") to unconditionally include in API requests.
// By default, fields with empty or default values are omitted from API
// requests. However, any non-pointer, non-interface field appearing in
// ForceSendFields will be sent to the server regardless of whether the
// field is empty or not. This may be used to include empty fields in
// Patch requests.
ForceSendFields []string `json:"-"`

// NullFields is a list of field names (e.g. "Disk") to include in API
// requests with the JSON null value. By default, fields with empty
// values are omitted from API requests. However, any field with an
// empty value appearing in NullFields will be sent to the server as
// null. It is an error if a field in this list has a non-empty value.
// This may be used to include null fields in Patch requests.
// NullFields is a list of field names (e.g. "ConsistencyGroupPolicy")
// to include in API requests with the JSON null value. By default,
// fields with empty values are omitted from API requests. However, any
// field with an empty value appearing in NullFields will be sent to the
// server as null. It is an error if a field in this list has a
// non-empty value. This may be used to include null fields in Patch
// requests.
NullFields []string `json:"-"`
}

Expand Down Expand Up @@ -38546,11 +38558,15 @@ type Quota struct {
// "NETWORK_ATTACHMENTS"
// "NETWORK_ENDPOINT_GROUPS"
// "NETWORK_FIREWALL_POLICIES"
// "NET_LB_SECURITY_POLICIES_PER_REGION"
// "NET_LB_SECURITY_POLICY_RULES_PER_REGION"
// "NET_LB_SECURITY_POLICY_RULE_ATTRIBUTES_PER_REGION"
// "NODE_GROUPS"
// "NODE_TEMPLATES"
// "NVIDIA_A100_80GB_GPUS"
// "NVIDIA_A100_GPUS"
// "NVIDIA_K80_GPUS"
// "NVIDIA_L4_GPUS"
// "NVIDIA_P100_GPUS"
// "NVIDIA_P100_VWS_GPUS"
// "NVIDIA_P4_GPUS"
Expand All @@ -38565,6 +38581,7 @@ type Quota struct {
// "PREEMPTIBLE_NVIDIA_A100_80GB_GPUS"
// "PREEMPTIBLE_NVIDIA_A100_GPUS"
// "PREEMPTIBLE_NVIDIA_K80_GPUS"
// "PREEMPTIBLE_NVIDIA_L4_GPUS"
// "PREEMPTIBLE_NVIDIA_P100_GPUS"
// "PREEMPTIBLE_NVIDIA_P100_VWS_GPUS"
// "PREEMPTIBLE_NVIDIA_P4_GPUS"
Expand All @@ -38589,6 +38606,7 @@ type Quota struct {
// "ROUTES"
// "SECURITY_POLICIES"
// "SECURITY_POLICIES_PER_REGION"
// "SECURITY_POLICY_ADVANCED_RULES_PER_REGION"
// "SECURITY_POLICY_CEVAL_RULES"
// "SECURITY_POLICY_RULES"
// "SECURITY_POLICY_RULES_PER_REGION"
Expand Down
40 changes: 39 additions & 1 deletion container/v1/container-api.json
Expand Up @@ -2487,7 +2487,7 @@
}
}
},
"revision": "20230304",
"revision": "20230322",
"rootUrl": "https://container.googleapis.com/",
"schemas": {
"AcceleratorConfig": {
Expand All @@ -2514,6 +2514,12 @@
},
"type": "object"
},
"AdditionalPodRangesConfig": {
"description": "AdditionalPodRangesConfig is the configuration for additional pod secondary ranges supporting the ClusterUpdate message.",
"id": "AdditionalPodRangesConfig",
"properties": {},
"type": "object"
},
"AddonsConfig": {
"description": "Configuration for the addons that can be automatically spun up in the cluster, enabling additional functionality.",
"id": "AddonsConfig",
Expand Down Expand Up @@ -3191,6 +3197,10 @@
"description": "ClusterUpdate describes an update to the cluster. Exactly one update can be applied to a cluster with each request, so at most one field can be provided.",
"id": "ClusterUpdate",
"properties": {
"additionalPodRangesConfig": {
"$ref": "AdditionalPodRangesConfig",
"description": "The additional pod ranges to be added to the cluster. These pod ranges can be used by node pools to allocate pod IPs."
},
"desiredAddonsConfig": {
"$ref": "AddonsConfig",
"description": "Configurations for the various addons available to run in the cluster."
Expand Down Expand Up @@ -3385,6 +3395,10 @@
"etag": {
"description": "The current etag of the cluster. If an etag is provided and does not match the current etag of the cluster, update will be blocked and an ABORTED error will be returned.",
"type": "string"
},
"removedAdditionalPodRangesConfig": {
"$ref": "AdditionalPodRangesConfig",
"description": "The additional pod ranges that are to be removed from the cluster. The pod ranges specified here must have been specified earlier in the 'additional_pod_ranges_config' argument."
}
},
"type": "object"
Expand Down Expand Up @@ -3907,6 +3921,11 @@
"description": "Configuration for controlling how IPs are allocated in the cluster.",
"id": "IPAllocationPolicy",
"properties": {
"additionalPodRangesConfig": {
"$ref": "AdditionalPodRangesConfig",
"description": "Output only. [Output only] The additional pod ranges that are added to the cluster. These pod ranges can be used by new node pools to allocate pod IPs automatically. Once the range is removed it will not show up in IPAllocationPolicy.",
"readOnly": true
},
"clusterIpv4Cidr": {
"description": "This field is deprecated, use cluster_ipv4_cidr_block.",
"type": "string"
Expand Down Expand Up @@ -3945,6 +3964,10 @@
"description": "The IP address range of the instance IPs in this cluster. This is applicable only if `create_subnetwork` is true. Set to blank to have a range chosen with the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) from the RFC-1918 private networks (e.g. `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`) to pick a specific range to use.",
"type": "string"
},
"podCidrOverprovisionConfig": {
"$ref": "PodCIDROverprovisionConfig",
"description": "[PRIVATE FIELD] Pod CIDR size overprovisioning config for the cluster. Pod CIDR size per node depends on max_pods_per_node. By default, the value of max_pods_per_node is doubled and then rounded off to next power of 2 to get the size of pod CIDR block per node. Example: max_pods_per_node of 30 would result in 64 IPs (/26). This config can disable the doubling of IPs (we still round off to next power of 2) Example: max_pods_per_node of 30 will result in 32 IPs (/27) when overprovisioning is disabled."
},
"servicesIpv4Cidr": {
"description": "This field is deprecated, use services_ipv4_cidr_block.",
"type": "string"
Expand Down Expand Up @@ -4862,6 +4885,10 @@
"$ref": "NetworkPerformanceConfig",
"description": "Network bandwidth tier configuration."
},
"podCidrOverprovisionConfig": {
"$ref": "PodCIDROverprovisionConfig",
"description": "[PRIVATE FIELD] Pod CIDR size overprovisioning config for the nodepool. Pod CIDR size per node depends on max_pods_per_node. By default, the value of max_pods_per_node is rounded off to next power of 2 and we then double that to get the size of pod CIDR block per node. Example: max_pods_per_node of 30 would result in 64 IPs (/26). This config can disable the doubling of IPs (we still round off to next power of 2) Example: max_pods_per_node of 30 will result in 32 IPs (/27) when overprovisioning is disabled."
},
"podIpv4CidrBlock": {
"description": "The IP address range for pod IPs in this node pool. Only applicable if `create_pod_range` is true. Set to blank to have a range chosen with the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) to pick a specific range to use. Only applicable if `ip_allocation_policy.use_ip_aliases` is true. This field cannot be changed after the node pool has been created.",
"type": "string"
Expand Down Expand Up @@ -5313,6 +5340,17 @@
},
"type": "object"
},
"PodCIDROverprovisionConfig": {
"description": "[PRIVATE FIELD] Config for pod CIDR size overprovisioning.",
"id": "PodCIDROverprovisionConfig",
"properties": {
"disable": {
"description": "Whether Pod CIDR overprovisioning is disabled. Note: Pod CIDR overprovisioning is enabled by default.",
"type": "boolean"
}
},
"type": "object"
},
"PrivateClusterConfig": {
"description": "Configuration options for private clusters.",
"id": "PrivateClusterConfig",
Expand Down