Arun Patel authored 3 years ago and Wajdi Hajji committed 3 years ago

This works with Terraform v0.14.10; the data source is read before
the plan walk, so the existing deployed image can be determined.
However, it is suggested that future Terraform may combine the
refresh and plan walks which *may* result in a cyclic dependancy.

Arun Patel authored 3 years ago and Wajdi Hajji committed 3 years ago

This works with Terraform v0.14.10; the data source is read before
the plan walk, so the existing deployed image can be determined.
However, it is suggested that future Terraform may combine the
refresh and plan walks which *may* result in a cyclic dependancy.

This works with Terraform v0.14.10; the data source is read before
the plan walk, so the existing deployed image can be determined.
However, it is suggested that future Terraform may combine the
refresh and plan walks which *may* result in a cyclic dependancy.

Do not remove the BETA stage as we are going to still use some BETA options like the mounting of secrets from GCP Secret Manager

Rather than ship our own monitoring module, make use of the
gcp-site-monitoring module. This effectively makes this module require
0.13 so a major version bump is required.

Closes #13

Allow an optional domain mapping to be configured for the webapp. If a
domain mapping is configured, appropriate DNS records are provided as
outputs.

Closes #2

This module manages a Cloud Run-hosted container. It takes care of making
sure the container is connected to a Cloud SQL instance and sets
environment variables on the application.