All Downloads are FREE. Search and download functionalities are using the official Maven repository.

target.apidocs.com.google.api.services.compute.Compute.Subnetworks.Patch.html Maven / Gradle / Ivy







Compute.Subnetworks.Patch (Compute Engine API beta-rev20220726-2.0.0)












com.google.api.services.compute

Class Compute.Subnetworks.Patch

    • Constructor Detail

      • Patch

        protected Patch(String project,
                        String region,
                        String subnetwork,
                        Subnetwork content)
        Patches the specified subnetwork with the data included in the request. Only certain fields can be updated with a patch request as indicated in the field descriptions. You must specify the current fingerprint of the subnetwork resource being patched. Create a request for the method "subnetworks.patch". This request holds the parameters needed by the the compute server. After setting any optional parameters, call the AbstractGoogleClientRequest.execute() method to invoke the remote operation.

        Compute.initialize(com.google.api.client.googleapis.services.AbstractGoogleClientRequest) must be called to initialize this instance immediately after invoking the constructor.

        Parameters:
        project - Project ID for this request.
        region - Name of the region scoping this request.
        subnetwork - Name of the Subnetwork resource to patch.
        content - the Subnetwork
        Since:
        1.13
    • Method Detail

      • getProject

        public String getProject()
        Project ID for this request.
      • getRegion

        public String getRegion()
        Name of the region scoping this request.
      • getSubnetwork

        public String getSubnetwork()
        Name of the Subnetwork resource to patch.
      • getDrainTimeoutSeconds

        public Integer getDrainTimeoutSeconds()
        The drain timeout specifies the upper bound in seconds on the amount of time allowed to drain connections from the current ACTIVE subnetwork to the current BACKUP subnetwork. The drain timeout is only applicable when the following conditions are true: - the subnetwork being patched has purpose = INTERNAL_HTTPS_LOAD_BALANCER - the subnetwork being patched has role = BACKUP - the patch request is setting the role to ACTIVE. Note that after this patch operation the roles of the ACTIVE and BACKUP subnetworks will be swapped.
      • setDrainTimeoutSeconds

        public Compute.Subnetworks.Patch setDrainTimeoutSeconds(Integer drainTimeoutSeconds)
        The drain timeout specifies the upper bound in seconds on the amount of time allowed to drain connections from the current ACTIVE subnetwork to the current BACKUP subnetwork. The drain timeout is only applicable when the following conditions are true: - the subnetwork being patched has purpose = INTERNAL_HTTPS_LOAD_BALANCER - the subnetwork being patched has role = BACKUP - the patch request is setting the role to ACTIVE. Note that after this patch operation the roles of the ACTIVE and BACKUP subnetworks will be swapped.
      • getRequestId

        public String getRequestId()
        An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
      • setRequestId

        public Compute.Subnetworks.Patch setRequestId(String requestId)
        An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).

Copyright © 2011–2022 Google. All rights reserved.





© 2015 - 2025 Weber Informatics LLC | Privacy Policy