Ignoring changes in name means that one can never run terraform
deployments beyond the initial creation of the webapp service. Terraform
will always modify a service in-place but try to use the same name which
negates the point of *setting* the name in the
google_cloud_run_service.webapp resource.

The downside of this is that one can't then deploy changes without
deleting and re-creating random_id.webapp_revision_name resource but
that is at least documented in the README.

Resolve CI changes not being ignored by terraform

Closes #3

See merge request !3

Add optional domain mapping

Closes #2

See merge request !2

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

GCP Cloud Run manager terraform module

Closes #1

See merge request !1

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.