diff --git a/docs/dyn/alloydb_v1alpha.projects.locations.clusters.html b/docs/dyn/alloydb_v1alpha.projects.locations.clusters.html index 1a616b8057..e901649cdb 100644 --- a/docs/dyn/alloydb_v1alpha.projects.locations.clusters.html +++ b/docs/dyn/alloydb_v1alpha.projects.locations.clusters.html @@ -212,6 +212,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -403,6 +406,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -643,6 +649,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -814,6 +823,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -994,6 +1006,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -1235,6 +1250,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. diff --git a/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html b/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html index 45e4a36def..30c5afdb2c 100644 --- a/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html +++ b/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html @@ -184,25 +184,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -332,25 +317,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -571,25 +541,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -770,25 +725,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -907,25 +847,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. diff --git a/docs/dyn/alloydb_v1beta.projects.locations.clusters.html b/docs/dyn/alloydb_v1beta.projects.locations.clusters.html index a71727e7fa..a4e7a3ea75 100644 --- a/docs/dyn/alloydb_v1beta.projects.locations.clusters.html +++ b/docs/dyn/alloydb_v1beta.projects.locations.clusters.html @@ -212,6 +212,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -402,6 +405,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -641,6 +647,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -811,6 +820,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -990,6 +1002,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. @@ -1230,6 +1245,9 @@

Method Details

"labels": { # Labels as key value pairs "a_key": "A String", }, + "maintenanceSchedule": { # 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. # Output only. The maintenance schedule for the cluster, generated for a specific rollout if a maintenance window is set. + "startTime": "A String", # Output only. The scheduled start time for the maintenance. + }, "maintenanceUpdatePolicy": { # MaintenanceUpdatePolicy defines the policy for system updates. # Optional. The maintenance update policy determines when to allow or deny updates. "denyMaintenancePeriods": [ # Periods to deny maintenance. Currently limited to 1. { # DenyMaintenancePeriod definition. Excepting emergencies, maintenance will not be scheduled to start within this deny period. The start_date must be less than the end_date. diff --git a/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html b/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html index 9b2f3daea7..c836e11686 100644 --- a/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html +++ b/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html @@ -184,25 +184,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -331,25 +316,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -569,25 +539,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -767,25 +722,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. @@ -903,25 +843,10 @@

Method Details

"trackWaitEvents": True or False, # Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on. }, "pscInstanceConfig": { # PscInstanceConfig contains PSC related configuration at an instance level. # Optional. The configuration for Private Service Connect (PSC) for the instance. - "allowedConsumerNetworks": [ # Optional. List of consumer networks that are allowed to create PSC endpoints to service-attachments to this instance. - "A String", - ], "allowedConsumerProjects": [ # Optional. List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. "A String", ], - "outgoingServiceAttachmentLinks": [ # 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. - "A String", - ], "pscDnsName": "A String", # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog - "pscEnabled": True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster. - "pscInterfaceConfigs": [ # 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. - { # 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. - "consumerEndpointIps": [ # 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. - "A String", - ], - "networkAttachment": "A String", # 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. - }, - ], "serviceAttachmentLink": "A String", # 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/` }, "publicIpAddress": "A String", # Output only. The public IP addresses for the Instance. This is available ONLY when enable_public_ip is set. This is the connection endpoint for an end-user application. diff --git a/googleapiclient/discovery_cache/documents/alloydb.v1.json b/googleapiclient/discovery_cache/documents/alloydb.v1.json index 50aa601ccc..98156f5774 100644 --- a/googleapiclient/discovery_cache/documents/alloydb.v1.json +++ b/googleapiclient/discovery_cache/documents/alloydb.v1.json @@ -1461,7 +1461,7 @@ } } }, -"revision": "20240315", +"revision": "20240320", "rootUrl": "https://alloydb.googleapis.com/", "schemas": { "AuthorizedNetwork": { diff --git a/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json b/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json index ea837754a9..3516e1eba9 100644 --- a/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json +++ b/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json @@ -1461,7 +1461,7 @@ } } }, -"revision": "20240315", +"revision": "20240320", "rootUrl": "https://alloydb.googleapis.com/", "schemas": { "AuthorizedNetwork": { @@ -1865,6 +1865,11 @@ false "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." @@ -2706,6 +2711,19 @@ false }, "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", @@ -3000,13 +3018,6 @@ false "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": { @@ -3014,29 +3025,11 @@ false }, "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, @@ -3045,24 +3038,6 @@ false }, "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", diff --git a/googleapiclient/discovery_cache/documents/alloydb.v1beta.json b/googleapiclient/discovery_cache/documents/alloydb.v1beta.json index 0295481fa3..d13239f73d 100644 --- a/googleapiclient/discovery_cache/documents/alloydb.v1beta.json +++ b/googleapiclient/discovery_cache/documents/alloydb.v1beta.json @@ -1458,7 +1458,7 @@ } } }, -"revision": "20240315", +"revision": "20240320", "rootUrl": "https://alloydb.googleapis.com/", "schemas": { "AuthorizedNetwork": { @@ -1851,6 +1851,11 @@ false "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." @@ -2682,6 +2687,19 @@ false }, "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", @@ -2976,13 +2994,6 @@ false "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": { @@ -2990,29 +3001,11 @@ false }, "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, @@ -3021,24 +3014,6 @@ false }, "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",