docs: add vpc peering examples for GCP and AWS

fixes #62

Author: rjeczalik

docs/resources/cluster.md

@@ -47,7 +47,7 @@ output "scylladbcloud_cluster_datacenter" {
 ### Optional
 
 - `alternator_write_isolation` (String) Default write isolation policy
-- `byoa_id` (Number) BYOA credential ID
+- `byoa_id` (Number) BYOA credential ID (only for AWS)
 - `cidr_block` (String) IPv4 CIDR of the cluster
 - `cloud` (String) Cluster name
 - `enable_dns` (Boolean) Whether to enable CNAME for seed nodes

docs/resources/vpc_peering.md

@@ -12,7 +12,7 @@ description: |-
 ## Example Usage
 
 ```terraform
-# Create a VPC peering connection top the specified datacenter.
+# Create a VPC peering connection to the specified datacenter.
 resource "scylladbcloud_vpc_peering" "example" {
 	cluster_id = 1337
 	datacenter = "AWS_US_EAST_1"
@@ -30,6 +30,70 @@ output "scylladbcloud_vpc_peering_connection_id" {
 }
 ```
 
+## Example Usage for AWS
+
+```terraform
+# End-to-end example for ScyllaDB Datacenter VPC peering on AWS.
+resource "aws_vpc" "app" {
+	cidr_block = "10.0.0.0/16"
+}
+
+data "aws_caller_identity" "current" {}
+
+resource "scylladbcloud_vpc_peering" "example" {
+	cluster_id = 1337
+	datacenter = "AWS_EAST_1"
+
+	peer_vpc_id     = aws_vpc.app.id
+	peer_cidr_block = aws_vpc.app.cidr_block
+	peer_region     = "us-east-1"
+	peer_account_id = data.aws_caller_identity.current.account_id
+
+	allow_cql = true
+}
+
+resource "aws_vpc_peering_connection_accepter" "app" {
+    vpc_peering_connection_id = scylladbcloud_vpc_peering.example.connection_id
+    auto_accept               = true
+}
+
+resource "aws_route_table" "bench" {
+	vpc_id = aws_vpc.app.id
+
+	route {
+		cidr_block = scylladbcloud_cluster.example.cidr_block
+		vpc_peering_connection_id = aws_vpc_peering_connection_accepter.app.vpc_peering_connection_id
+	}
+}
+```
+
+## Example Usage for GCP
+
+```terraform
+# End-to-end example for ScyllaDB Datacenter network peering on GCP.
+resource "google_compute_network" "app" {
+	name = "app"
+	auto_create_subnetworks = true
+}
+
+resource "scylladbcloud_vpc_peering" "example" {
+	cluster_id = 1337
+	datacenter = "GCE_US_CENTRAL_1"
+
+	peer_vpc_id     = google_compute_network.app.name
+	peer_region     = "us-central1"
+	peer_account_id = "exampleproject"
+
+	allow_cql = true
+}
+
+resource "google_compute_network_peering" "app" {
+	name         = "app-peering"
+	network      = google_compute_network.app.self_link
+	peer_network = scylladbcloud_vpc_peering.example.network_link
+}
+```
+
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
@@ -38,19 +102,20 @@ output "scylladbcloud_vpc_peering_connection_id" {
 - `cluster_id` (Number) Cluster ID
 - `datacenter` (String) Cluster datacenter name
 - `peer_account_id` (String) Peer Account ID
-- `peer_cidr_block` (String) Peer VPC CIDR block
 - `peer_region` (String) Peer VPC region
 - `peer_vpc_id` (String) Peer VPC ID
 
 ### Optional
 
 - `allow_cql` (Boolean) Whether to allow CQL traffic
+- `peer_cidr_block` (String) Peer VPC CIDR block
 - `timeouts` (Block, Optional) (see [below for nested schema](#nestedblock--timeouts))
 
 ### Read-Only
 
 - `connection_id` (String) VPC peering connection id
 - `id` (String) The ID of this resource.
+- `network_link` (String) (GCP) Cluster VPC network self_link
 - `vpc_peering_id` (Number) Cluster VPC Peering ID
 
 <a id="nestedblock--timeouts"></a>

examples/resources/scylladbcloud_vpc_peering/aws.tf

@@ -0,0 +1,32 @@
+# End-to-end example for ScyllaDB Datacenter VPC peering on AWS.
+resource "aws_vpc" "app" {
+	cidr_block = "10.0.0.0/16"
+}
+
+data "aws_caller_identity" "current" {}
+
+resource "scylladbcloud_vpc_peering" "example" {
+	cluster_id = 1337
+	datacenter = "AWS_EAST_1"
+
+	peer_vpc_id     = aws_vpc.app.id
+	peer_cidr_block = aws_vpc.app.cidr_block
+	peer_region     = "us-east-1"
+	peer_account_id = data.aws_caller_identity.current.account_id
+
+	allow_cql = true
+}
+
+resource "aws_vpc_peering_connection_accepter" "app" {
+    vpc_peering_connection_id = scylladbcloud_vpc_peering.example.connection_id
+    auto_accept               = true
+}
+
+resource "aws_route_table" "bench" {
+	vpc_id = aws_vpc.app.id
+
+	route {
+		cidr_block = scylladbcloud_cluster.example.cidr_block
+		vpc_peering_connection_id = aws_vpc_peering_connection_accepter.app.vpc_peering_connection_id
+	}
+}

examples/resources/scylladbcloud_vpc_peering/gcp.tf

@@ -0,0 +1,22 @@
+# End-to-end example for ScyllaDB Datacenter network peering on GCP.
+resource "google_compute_network" "app" {
+	name = "app"
+	auto_create_subnetworks = true
+}
+
+resource "scylladbcloud_vpc_peering" "example" {
+	cluster_id = 1337
+	datacenter = "GCE_US_CENTRAL_1"
+
+	peer_vpc_id     = google_compute_network.app.name
+	peer_region     = "us-central1"
+	peer_account_id = "exampleproject"
+
+	allow_cql = true
+}
+
+resource "google_compute_network_peering" "app" {
+	name         = "app-peering"
+	network      = google_compute_network.app.self_link
+	peer_network = scylladbcloud_vpc_peering.example.network_link
+}

templates/resources/vpc_peering.md.tmpl

@@ -13,6 +13,14 @@ description: |-
 
 {{ tffile (printf "examples/resources/%s/resource.tf" .Name)}}
 
+## Example Usage for AWS
+
+{{ tffile (printf "examples/resources/%s/aws.tf" .Name)}}
+
+## Example Usage for GCP
+
+{{ tffile (printf "examples/resources/%s/gcp.tf" .Name)}}
+
 {{ .SchemaMarkdown | trimspace }}
 
 ## Import