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.

Update the changelog for 3.1.1

See merge request !28

Surface the alerting percentage variable.

See merge request !26

Add secretAccessor IAM permissions to Cloud Run Service account

Closes #22

See merge request !27

Resolve "Support loading secrets directly into services"

Closes #20

See merge request !25

Merge branch '18-terraform-always-wants-to-add-metadata-annotation-run-googleapis-com-launch-stage-beta' into 'master'

Resolve "Terraform always wants to add  metadata annotation "run.googleapis.com/launch-stage"   = "BETA""

Closes #18

See merge request !24

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

use gvisor instead of placeholder

Closes #17

See merge request !23

Update changelog for 2.0.3

See merge request !22

Add flag to stop egress ip being destroyed

Closes #16

See merge request !21

Update changelog

See merge request !20

Configure monitoring authentication proxy for instances which require authentication

See merge request !19

add additional attrbutes to ignore changes list

See merge request !17

Allow static egress ip

Closes #15

See merge request !18

There are a few more attributes which Google has started using
internally to record state. Add them to the ignore changes list so that
terraform won't keep wanting to change resources.

Part of uis/devops/raven/infrastructure#32

make use of our common monitoring module

Closes #13

See merge request !15

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

Use Google Beta provider to allow for min-scale option

See merge request !16