Class: Google::Cloud::Compute::V1::NetworkPeeringConnectionStatus

Inherits:

Object

• Object
• Google::Cloud::Compute::V1::NetworkPeeringConnectionStatus

Extended by:

Protobuf::MessageExts::ClassMethods

Includes:

Protobuf::MessageExts

Defined in:

proto_docs/google/cloud/compute/v1/compute.rb

Overview

[Output Only] Describes the state of a peering connection, not just the local peering. This field provides information about the effective settings for the connection as a whole, including pending delete/update requests for CONSENSUS peerings.

Defined Under Namespace

Modules: UpdateStrategy

Instance Attribute Summary

• #consensus_state ⇒ ::Google::Cloud::Compute::V1::NetworkPeeringConnectionStatusConsensusState

  The consensus state contains information about the status of update and delete for a consensus peering connection.

• #traffic_configuration ⇒ ::Google::Cloud::Compute::V1::NetworkPeeringConnectionStatusTrafficConfiguration

  The active connectivity settings for the peering connection based on the settings of the network peerings.

• #update_strategy ⇒ ::String

  The update strategy determines the update/delete semantics for this peering connection.

Instance Attribute Details

#consensus_state ⇒ ::Google::Cloud::Compute::V1::NetworkPeeringConnectionStatusConsensusState

# File 'proto_docs/google/cloud/compute/v1/compute.rb', line 23873

class NetworkPeeringConnectionStatus
  include ::Google::Protobuf::MessageExts
  extend ::Google::Protobuf::MessageExts::ClassMethods

  # The update strategy determines the update/delete semantics for this peering connection.
  module UpdateStrategy
    # A value indicating that the enum field is not set.
    UNDEFINED_UPDATE_STRATEGY = 0

    # Updates are reflected in the local peering but aren't applied to the peering connection until a complementary change is made to the matching peering. To delete a peering with the consensus update strategy, both the peerings must request the deletion of the peering before the peering can be deleted.
    CONSENSUS = 203_373_655

    # In this mode, changes to the peering configuration can be unilaterally altered by changing either side of the peering. This is the default value if the field is unspecified.
    INDEPENDENT = 127_011_674

    # Peerings with update strategy UNSPECIFIED are created with update strategy INDEPENDENT.
    UNSPECIFIED = 526_786_327
  end
end

#traffic_configuration ⇒ ::Google::Cloud::Compute::V1::NetworkPeeringConnectionStatusTrafficConfiguration

# File 'proto_docs/google/cloud/compute/v1/compute.rb', line 23873

class NetworkPeeringConnectionStatus
  include ::Google::Protobuf::MessageExts
  extend ::Google::Protobuf::MessageExts::ClassMethods

  # The update strategy determines the update/delete semantics for this peering connection.
  module UpdateStrategy
    # A value indicating that the enum field is not set.
    UNDEFINED_UPDATE_STRATEGY = 0

    # Updates are reflected in the local peering but aren't applied to the peering connection until a complementary change is made to the matching peering. To delete a peering with the consensus update strategy, both the peerings must request the deletion of the peering before the peering can be deleted.
    CONSENSUS = 203_373_655

    # In this mode, changes to the peering configuration can be unilaterally altered by changing either side of the peering. This is the default value if the field is unspecified.
    INDEPENDENT = 127_011_674

    # Peerings with update strategy UNSPECIFIED are created with update strategy INDEPENDENT.
    UNSPECIFIED = 526_786_327
  end
end

#update_strategy ⇒ ::String

# File 'proto_docs/google/cloud/compute/v1/compute.rb', line 23873

class NetworkPeeringConnectionStatus
  include ::Google::Protobuf::MessageExts
  extend ::Google::Protobuf::MessageExts::ClassMethods

  # The update strategy determines the update/delete semantics for this peering connection.
  module UpdateStrategy
    # A value indicating that the enum field is not set.
    UNDEFINED_UPDATE_STRATEGY = 0

    # Updates are reflected in the local peering but aren't applied to the peering connection until a complementary change is made to the matching peering. To delete a peering with the consensus update strategy, both the peerings must request the deletion of the peering before the peering can be deleted.
    CONSENSUS = 203_373_655

    # In this mode, changes to the peering configuration can be unilaterally altered by changing either side of the peering. This is the default value if the field is unspecified.
    INDEPENDENT = 127_011_674

    # Peerings with update strategy UNSPECIFIED are created with update strategy INDEPENDENT.
    UNSPECIFIED = 526_786_327
  end
end