Skip to content

Commit

Permalink
Add Network Management ConnectivityTest resource (#3601) (#54)
Browse files Browse the repository at this point in the history
* add filename override

* initial network management resource

* description

* comments

Signed-off-by: Modular Magician <magic-modules@google.com>
  • Loading branch information
modular-magician authored Jun 4, 2020
1 parent 9c807b2 commit b7999f1
Show file tree
Hide file tree
Showing 8 changed files with 301 additions and 0 deletions.
15 changes: 15 additions & 0 deletions network_management_connectivity_test_addresses/backing_file.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# This file has some scaffolding to make sure that names are unique and that
# a region and zone are selected when you try to create your Terraform resources.

locals {
name_suffix = "${random_pet.suffix.id}"
}

resource "random_pet" "suffix" {
length = 2
}

provider "google" {
region = "us-central1"
zone = "us-central1-c"
}
44 changes: 44 additions & 0 deletions network_management_connectivity_test_addresses/main.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
resource "google_network_management_connectivity_test" "address-test" {
name = "conn-test-addr-${local.name_suffix}"
source {
ip_address = google_compute_address.source-addr.address
project_id = google_compute_address.source-addr.project
network = google_compute_network.vpc.id
network_type = "GCP_NETWORK"
}

destination {
ip_address = google_compute_address.dest-addr.address
project_id = google_compute_address.dest-addr.project
network = google_compute_network.vpc.id
}

protocol = "UDP"
}

resource "google_compute_network" "vpc" {
name = "connectivity-vpc-${local.name_suffix}"
}

resource "google_compute_subnetwork" "subnet" {
name = "connectivity-vpc-${local.name_suffix}-subnet"
ip_cidr_range = "10.0.0.0/16"
region = "us-central1"
network = google_compute_network.vpc.id
}

resource "google_compute_address" "source-addr" {
name = "src-addr-${local.name_suffix}"
subnetwork = google_compute_subnetwork.subnet.id
address_type = "INTERNAL"
address = "10.0.42.42"
region = "us-central1"
}

resource "google_compute_address" "dest-addr" {
name = "dest-addr-${local.name_suffix}"
subnetwork = google_compute_subnetwork.subnet.id
address_type = "INTERNAL"
address = "10.0.43.43"
region = "us-central1"
}
7 changes: 7 additions & 0 deletions network_management_connectivity_test_addresses/motd
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
===

These examples use real resources that will be billed to the
Google Cloud Platform project you use - so make sure that you
run "terraform destroy" before quitting!

===
79 changes: 79 additions & 0 deletions network_management_connectivity_test_addresses/tutorial.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# Network Management Connectivity Test Addresses - Terraform

## Setup

<walkthrough-author name="rileykarson@google.com" analyticsId="UA-125550242-1" tutorialName="network_management_connectivity_test_addresses" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>

Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.

<walkthrough-project-billing-setup></walkthrough-project-billing-setup>

Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.

## Terraforming!

Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
the project name from the environment variable.

```bash
export GOOGLE_CLOUD_PROJECT={{project-id}}
```

After that, let's get Terraform started. Run the following to pull in the providers.

```bash
terraform init
```

With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!

```bash
terraform apply
```

Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.

```bash
yes
```


## Post-Apply

### Editing your config

Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.

```bash
terraform plan
```

So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
run a 'plan' again.

```bash
terraform plan
```

Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
at the 'yes' prompt.

```bash
terraform apply
```

```bash
yes
```

## Cleanup

Run the following to remove the resources Terraform provisioned:

```bash
terraform destroy
```
```bash
yes
```
15 changes: 15 additions & 0 deletions network_management_connectivity_test_instances/backing_file.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# This file has some scaffolding to make sure that names are unique and that
# a region and zone are selected when you try to create your Terraform resources.

locals {
name_suffix = "${random_pet.suffix.id}"
}

resource "random_pet" "suffix" {
length = 2
}

provider "google" {
region = "us-central1"
zone = "us-central1-c"
}
55 changes: 55 additions & 0 deletions network_management_connectivity_test_instances/main.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
resource "google_network_management_connectivity_test" "instance-test" {
name = "conn-test-instances-${local.name_suffix}"
source {
instance = google_compute_instance.source.id
}

destination {
instance = google_compute_instance.destination.id
}

protocol = "TCP"
}

resource "google_compute_instance" "source" {
name = "source-vm-${local.name_suffix}"
machine_type = "n1-standard-1"

boot_disk {
initialize_params {
image = data.google_compute_image.debian_9.self_link
}
}

network_interface {
network = google_compute_network.vpc.id
access_config {
}
}
}

resource "google_compute_instance" "destination" {
name = "dest-vm-${local.name_suffix}"
machine_type = "n1-standard-1"

boot_disk {
initialize_params {
image = data.google_compute_image.debian_9.self_link
}
}

network_interface {
network = google_compute_network.vpc.id
access_config {
}
}
}

resource "google_compute_network" "vpc" {
name = "conn-test-net-${local.name_suffix}"
}

data "google_compute_image" "debian_9" {
family = "debian-9"
project = "debian-cloud"
}
7 changes: 7 additions & 0 deletions network_management_connectivity_test_instances/motd
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
===

These examples use real resources that will be billed to the
Google Cloud Platform project you use - so make sure that you
run "terraform destroy" before quitting!

===
79 changes: 79 additions & 0 deletions network_management_connectivity_test_instances/tutorial.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# Network Management Connectivity Test Instances - Terraform

## Setup

<walkthrough-author name="rileykarson@google.com" analyticsId="UA-125550242-1" tutorialName="network_management_connectivity_test_instances" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>

Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.

<walkthrough-project-billing-setup></walkthrough-project-billing-setup>

Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.

## Terraforming!

Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
the project name from the environment variable.

```bash
export GOOGLE_CLOUD_PROJECT={{project-id}}
```

After that, let's get Terraform started. Run the following to pull in the providers.

```bash
terraform init
```

With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!

```bash
terraform apply
```

Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.

```bash
yes
```


## Post-Apply

### Editing your config

Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.

```bash
terraform plan
```

So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
run a 'plan' again.

```bash
terraform plan
```

Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
at the 'yes' prompt.

```bash
terraform apply
```

```bash
yes
```

## Cleanup

Run the following to remove the resources Terraform provisioned:

```bash
terraform destroy
```
```bash
yes
```

0 comments on commit b7999f1

Please sign in to comment.