make use of our common monitoring module

Rather than ship our own monitoring module, make use of the gcp-site-monitoring module. This effectively makes this module require terraform 0.13 so a major version bump is required. Once this is merged, "release" by opening a v2 branch and having the previous master be v1 as outlined in the README.

This will add monitoring for the auto-generated Cloud Run domain as well as any domain mappings. Allow monitoring to be disabled if, for example, the service is configured to disallow direct invocations.

Tested by upgrading the tlscerts deployment to terraform 0.13 (https://gitlab.developers.cam.ac.uk/uis/devops/tls-certificates/google-cloud-deploy/-/merge_requests/16) and deploying development:

Closes #13 (closed)

changed milestone to %DevOps Sprint 113

added 1 commit

• 562c902e - make use of our common monitoring module

Compare with previous version

changed the description

marked this merge request as draft

Moved to Draft while I tweak a couple of things...

added 1 commit

• bff0d880 - make use of our common monitoring module

Compare with previous version

added 1 commit

• 7372a649 - make use of our common monitoring module

Compare with previous version

marked this merge request as ready

changed the description

added 1 commit

• 8cb6c1c5 - make use of our common monitoring module

Compare with previous version

added 5 commits

• 8cb6c1c5...993db4d1 - 4 commits from branch master
• 1ff24a86 - make use of our common monitoring module

Compare with previous version

Rebased on current master to fix merge conflicts.

Required by https://gitlab.developers.cam.ac.uk/uis/devops/tls-certificates/google-cloud-deploy/-/issues/13