Method: networks.addPeering

Adds a peering to the specified network.

HTTP request

POST https://compute.s3nsapis.fr/compute/v1/projects/{project}/global/networks/{network}/addPeering

The URL uses gRPC Transcoding syntax. To know more about valid error responses that can be thrown by this HTTP request, please refer to the service error catalog

Path parameters

Parameters
project

string

Project ID for this request.
network

string

Name of the network resource to add peering to.

Query parameters

Parameters
requestId

string

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

).

Request body

The request body contains data with the following structure:

JSON representation 
{
  "name": string,
  "peerNetwork": string,
  "autoCreateRoutes": boolean,
  "networkPeering": {
    object (NetworkPeering)
  }
}
Fields
name

string

[REQUIRED] Name of the peering, which should conform to RFC1035.
peerNetwork

string

URL of the peer network. It can be either full URL or partial URL. The peer network may belong to a different project. If the partial URL does not contain project, it is assumed that the peer network is in the same project as the current network.
autoCreateRoutes

boolean

This field will be deprecated soon. Use

exchangeSubnetRoutes

in

networkPeering

instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Trusted Cloud Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is

ACTIVE

.
networkPeering

object (NetworkPeering)

Network peering parameters. In order to specify route policies for peering using import and export custom routes, you must specify all peering related parameters (

name

,

peer network

,

exchangeSubnetRoutes

) in the

networkPeering

field. The corresponding fields in NetworksAddPeeringRequest will be deprecated soon.

Response body

If successful, the response body contains an instance of Operation.

Authorization scopes

Requires one of the following OAuth scopes:

  • https://www.googleapis.com/auth/compute
  • https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.

IAM Permissions

In addition to any permissions specified on the fields above, authorization requires one or more of the following IAM permissions:

  • compute.networks.addPeering

To find predefined roles that contain those permissions, see Compute Engine IAM Roles.