This repository has been archived by the owner on Sep 16, 2020. It is now read-only.
0.2.0
Overview
- Support for HTTP/HTTPS/TCP load balancers
- It is now required to specify a list of regions as an input variable. FYI, this tooling is incompatible with the West region, because it only includes 2 zones whereas we require 3+
- Option to configure a Google Cloud SQL instance as an external ERT DB
Input changes
- Add
ssl_cert
for use with HTTPS LB - Add
ssl_cert_private_key
for use with HTTPS LB - Remove default value for
zones
, must be specified now - Add
sql_region
with defaultus-central
to work around bug where Google Cloud SQL will not accept the real region, us-central1.us-east1
,asia-west1
andeurope-west1
work fine. - Add
opsman_sql_db_username
for use with Google Cloud SQL DB. Defaults to empty string. - Add
opsman_sql_db_password
for use with Google Cloud SQL DB. Defaults to empty string. - Rename
google_sql_db_tier
tosql_db_tier
- Add
ert_sql_instance_count
. Defaults to 0. - Add
ert_sql_db_host
. Defaults to empty string. - Add
ert_sql_db_username
. Defaults to empty string. - Add
ert_sql_db_password
. Defaults to empty string.
Output changes
- Remove
router-pool
in favor of specific pools - Add
http_lb_backend_name
for http routing. Route to instances by configuring them with this tag on the Resource Config page for ERT. - Add
ws_router_pool
for websocket routing. Route to instances by configuring them with this tag on the Resource Config page for ERT. - Add
ssh_router_pool
for ssh routing. Route to instances by configuring them with this tag on the Resource Config page for ERT. - Add
ert_sql_username
for use with the Google Cloud SQL DB - Add
ert_sql_password
for use with the Google Cloud SQL DB - Rename
opsman_sql_db_ip
tosql_db_ip