There is no impact with this bump as the options we use are still supported.

The Cloud Run Domain Mapping service is still in Pre-GA status after
more than 3 years. Google's documentation now suggest using load balancers
or Firebase Hosting as an alternative as there are limitations with the domain mapping service.
We are removing it from this module as it seems as though it will soon be deprecated.

BREAKING CHANGE: Remove Cloud Run Domain Mapping

This commit refactors the uptime_monitoring module to no longer require
an additional "stackdriver" aliased google provider.
This was a source of confusion as it did some "magic" with regards to
passing project IDs around.
The two projects are now clearly defined as either `project` or
`monitoring_scoping_project` to avoid any confusion.

Allow max_throughput to be overridden for vpc_access_connector

See merge request !62

Switch to use Terraform-Module.gitlab-ci.yml. This provides the same...

See merge request !61

Switch to use terraform-module.yml. This provides the same functionality as the original script, namely to lint the Terraform with the addition of creating a Terraform Module if a commit tag is provided

Added missing 8.1.0 entry and moved new feature to 8.2.0

See merge request !60

Added new variable to allow pre-deploy job specific environment variables to be set

Closes #44

See merge request !59

Add database migration Cloud Run job config

See merge request !58

This is initially planned to execute Django database migrations. However,
other use cases will exist I'm sure.

Update CHANGELOG

See merge request !57

Upgrade to v3 of the gcp-site-monitoring-module

See merge request !56

BREAKING CHANGE: The default SSL policy restricts TLS to >= 1.2 and
sets the SSL profile to MODERN.

BREAKING CHANGE: Upgrading to v3 of the gcp-site-monitoring module
will cause uptime check functions to be destroyed/re-created during the
next Terraform apply.

Add load balancer ssl policy and output

See merge request !55

ignore operation-id annotation

Closes #40

See merge request !54

fix: broken for_each on initial deploy

Closes #39

See merge request !53

chore: update changelog for release 6.0.0

See merge request !52