90 lines
3.2 KiB
HCL
90 lines
3.2 KiB
HCL
# ------------------------------------------------------------------------------
|
|
# LAUNCH A POSTGRESQL CLOUD SQL PUBLIC IP INSTANCE
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# ------------------------------------------------------------------------------
|
|
# CONFIGURE OUR GCP CONNECTION
|
|
# ------------------------------------------------------------------------------
|
|
|
|
provider "google-beta" {
|
|
version = "~> 2.7.0"
|
|
project = var.project
|
|
region = var.region
|
|
}
|
|
|
|
terraform {
|
|
# The modules used in this example have been updated with 0.12 syntax, which means the example is no longer
|
|
# compatible with any versions below 0.12.
|
|
required_version = ">= 0.12"
|
|
}
|
|
|
|
# ------------------------------------------------------------------------------
|
|
# CREATE A RANDOM SUFFIX AND PREPARE RESOURCE NAMES
|
|
# ------------------------------------------------------------------------------
|
|
|
|
resource "random_id" "name" {
|
|
byte_length = 2
|
|
}
|
|
|
|
locals {
|
|
# If name_override is specified, use that - otherwise use the name_prefix with a random string
|
|
instance_name = var.name_override == null ? format("%s-%s", var.name_prefix, random_id.name.hex) : var.name_override
|
|
}
|
|
|
|
# ------------------------------------------------------------------------------
|
|
# CREATE DATABASE INSTANCE WITH PUBLIC IP
|
|
# ------------------------------------------------------------------------------
|
|
|
|
module "postgres" {
|
|
# When using these modules in your own templates, you will need to use a Git URL with a ref attribute that pins you
|
|
# to a specific version of the modules, such as the following example:
|
|
# source = "github.com/gruntwork-io/terraform-google-sql.git//modules/cloud-sql?ref=v0.2.0"
|
|
source = "../../modules/cloud-sql"
|
|
|
|
project = var.project
|
|
region = var.region
|
|
name = local.instance_name
|
|
db_name = var.db_name
|
|
|
|
engine = var.postgres_version
|
|
machine_type = var.machine_type
|
|
|
|
# These together will construct the master_user privileges, i.e.
|
|
# 'master_user_name'@'master_user_host' IDENTIFIED BY 'master_user_password'.
|
|
# These should typically be set as the environment variable TF_VAR_master_user_password, etc.
|
|
# so you don't check these into source control."
|
|
master_user_password = var.master_user_password
|
|
|
|
master_user_name = var.master_user_name
|
|
master_user_host = "%"
|
|
|
|
# To make it easier to test this example, we are giving the servers public IP addresses and allowing inbound
|
|
# connections from anywhere. In real-world usage, your servers should live in private subnets, only have private IP
|
|
# addresses, and only allow access from specific trusted networks, servers or applications in your VPC.
|
|
enable_public_internet_access = true
|
|
|
|
# Default setting for this is 'false' in 'variables.tf'
|
|
# In the test cases, we're setting this to true, to test forced SSL.
|
|
require_ssl = var.require_ssl
|
|
|
|
authorized_networks = [
|
|
{
|
|
name = "allow-all-inbound"
|
|
value = "0.0.0.0/0"
|
|
},
|
|
]
|
|
|
|
# Set test flags
|
|
# Cloud SQL will complain if they're not applicable to the engine
|
|
database_flags = [
|
|
{
|
|
name = "autovacuum_naptime"
|
|
value = "2"
|
|
},
|
|
]
|
|
|
|
custom_labels = {
|
|
test-id = "postgres-public-ip-example"
|
|
}
|
|
}
|