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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 1 commit into from
Mar 31, 2024
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
63 changes: 19 additions & 44 deletions alloydb/v1alpha/alloydb-api.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1461,7 +1461,7 @@
}
}
},
"revision": "20240315",
"revision": "20240320",
"rootUrl": "https://alloydb.googleapis.com/",
"schemas": {
"AuthorizedNetwork": {
Expand Down Expand Up @@ -1865,6 +1865,11 @@
"description": "Labels as key value pairs",
"type": "object"
},
"maintenanceSchedule": {
"$ref": "MaintenanceSchedule",
"description": "Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set.",
"readOnly": true
},
"maintenanceUpdatePolicy": {
"$ref": "MaintenanceUpdatePolicy",
"description": "Optional. The maintenance update policy determines when to allow or deny updates."
Expand Down Expand Up @@ -2706,6 +2711,19 @@
},
"type": "object"
},
"MaintenanceSchedule": {
"description": "MaintenanceSchedule stores the maintenance schedule generated from the MaintenanceUpdatePolicy, once a maintenance rollout is triggered, if MaintenanceWindow is set, and if there is no conflicting DenyPeriod. The schedule is cleared once the update takes place. This field cannot be manually changed; modify the MaintenanceUpdatePolicy instead.",
"id": "MaintenanceSchedule",
"properties": {
"startTime": {
"description": "Output only. The scheduled start time for the maintenance.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
}
},
"type": "object"
},
"MaintenanceUpdatePolicy": {
"description": "MaintenanceUpdatePolicy defines the policy for system updates.",
"id": "MaintenanceUpdatePolicy",
Expand Down Expand Up @@ -3000,43 +3018,18 @@
"description": "PscInstanceConfig contains PSC related configuration at an instance level.",
"id": "PscInstanceConfig",
"properties": {
"allowedConsumerNetworks": {
"description": "Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance.",
"items": {
"type": "string"
},
"type": "array"
},
"allowedConsumerProjects": {
"description": "Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance.",
"items": {
"type": "string"
},
"type": "array"
},
"outgoingServiceAttachmentLinks": {
"description": "Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.",
"items": {
"type": "string"
},
"type": "array"
},
"pscDnsName": {
"description": "Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog",
"readOnly": true,
"type": "string"
},
"pscEnabled": {
"description": "Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.",
"type": "boolean"
},
"pscInterfaceConfigs": {
"description": "Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.",
"items": {
"$ref": "PscInterfaceConfig"
},
"type": "array"
},
"serviceAttachmentLink": {
"description": "Output only. The service attachment created when Private Service Connect (PSC) is enabled for the instance. The name of the resource will be in the format of `projects//regions//serviceAttachments/`",
"readOnly": true,
Expand All @@ -3045,24 +3038,6 @@
},
"type": "object"
},
"PscInterfaceConfig": {
"description": "Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.",
"id": "PscInterfaceConfig",
"properties": {
"consumerEndpointIps": {
"description": "A list of endpoints in the consumer VPC the interface might initiate outbound connections to. This list has to be provided when the PSC interface is created.",
"items": {
"type": "string"
},
"type": "array"
},
"networkAttachment": {
"description": "The NetworkAttachment resource created in the consumer VPC to which the PSC interface will be linked, in the form of: `projects/${CONSUMER_PROJECT}/regions/${REGION}/networkAttachments/${NETWORK_ATTACHMENT_NAME}`. NetworkAttachment has to be provided when the PSC interface is created.",
"type": "string"
}
},
"type": "object"
},
"QuantityBasedExpiry": {
"description": "A backup's position in a quantity-based retention queue, of backups with the same source cluster and type, with length, retention, specified by the backup's retention policy. Once the position is greater than the retention, the backup is eligible to be garbage collected. Example: 5 backups from the same source cluster and type with a quantity-based retention of 3 and denoted by backup_id (position, retention). Safe: backup_5 (1, 3), backup_4, (2, 3), backup_3 (3, 3). Awaiting garbage collection: backup_2 (4, 3), backup_1 (5, 3)",
"id": "QuantityBasedExpiry",
Expand Down
107 changes: 40 additions & 67 deletions alloydb/v1alpha/alloydb-gen.go
View file
Open in desktop

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

63 changes: 19 additions & 44 deletions alloydb/v1beta/alloydb-api.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1458,7 +1458,7 @@
}
}
},
"revision": "20240315",
"revision": "20240320",
"rootUrl": "https://alloydb.googleapis.com/",
"schemas": {
"AuthorizedNetwork": {
Expand Down Expand Up @@ -1851,6 +1851,11 @@
"description": "Labels as key value pairs",
"type": "object"
},
"maintenanceSchedule": {
"$ref": "MaintenanceSchedule",
"description": "Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set.",
"readOnly": true
},
"maintenanceUpdatePolicy": {
"$ref": "MaintenanceUpdatePolicy",
"description": "Optional. The maintenance update policy determines when to allow or deny updates."
Expand Down Expand Up @@ -2682,6 +2687,19 @@
},
"type": "object"
},
"MaintenanceSchedule": {
"description": "MaintenanceSchedule stores the maintenance schedule generated from the MaintenanceUpdatePolicy, once a maintenance rollout is triggered, if MaintenanceWindow is set, and if there is no conflicting DenyPeriod. The schedule is cleared once the update takes place. This field cannot be manually changed; modify the MaintenanceUpdatePolicy instead.",
"id": "MaintenanceSchedule",
"properties": {
"startTime": {
"description": "Output only. The scheduled start time for the maintenance.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
}
},
"type": "object"
},
"MaintenanceUpdatePolicy": {
"description": "MaintenanceUpdatePolicy defines the policy for system updates.",
"id": "MaintenanceUpdatePolicy",
Expand Down Expand Up @@ -2976,43 +2994,18 @@
"description": "PscInstanceConfig contains PSC related configuration at an instance level.",
"id": "PscInstanceConfig",
"properties": {
"allowedConsumerNetworks": {
"description": "Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance.",
"items": {
"type": "string"
},
"type": "array"
},
"allowedConsumerProjects": {
"description": "Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance.",
"items": {
"type": "string"
},
"type": "array"
},
"outgoingServiceAttachmentLinks": {
"description": "Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.",
"items": {
"type": "string"
},
"type": "array"
},
"pscDnsName": {
"description": "Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog",
"readOnly": true,
"type": "string"
},
"pscEnabled": {
"description": "Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.",
"type": "boolean"
},
"pscInterfaceConfigs": {
"description": "Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.",
"items": {
"$ref": "PscInterfaceConfig"
},
"type": "array"
},
"serviceAttachmentLink": {
"description": "Output only. The service attachment created when Private Service Connect (PSC) is enabled for the instance. The name of the resource will be in the format of `projects//regions//serviceAttachments/`",
"readOnly": true,
Expand All @@ -3021,24 +3014,6 @@
},
"type": "object"
},
"PscInterfaceConfig": {
"description": "Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.",
"id": "PscInterfaceConfig",
"properties": {
"consumerEndpointIps": {
"description": "A list of endpoints in the consumer VPC the interface might initiate outbound connections to. This list has to be provided when the PSC interface is created.",
"items": {
"type": "string"
},
"type": "array"
},
"networkAttachment": {
"description": "The NetworkAttachment resource created in the consumer VPC to which the PSC interface will be linked, in the form of: `projects/${CONSUMER_PROJECT}/regions/${REGION}/networkAttachments/${NETWORK_ATTACHMENT_NAME}`. NetworkAttachment has to be provided when the PSC interface is created.",
"type": "string"
}
},
"type": "object"
},
"QuantityBasedExpiry": {
"description": "A backup's position in a quantity-based retention queue, of backups with the same source cluster and type, with length, retention, specified by the backup's retention policy. Once the position is greater than the retention, the backup is eligible to be garbage collected. Example: 5 backups from the same source cluster and type with a quantity-based retention of 3 and denoted by backup_id (position, retention). Safe: backup_5 (1, 3), backup_4, (2, 3), backup_3 (3, 3). Awaiting garbage collection: backup_2 (4, 3), backup_1 (5, 3)",
"id": "QuantityBasedExpiry",
Expand Down