v1.2.9

🚀 Enhancements

Document `google_netblock_ip_ranges` data source @kpocius (#91)

what

• Document google_netblock_ip_ranges data source added in #88
• Trim whitespace & remove trailing punctuation

why

• Trailing punctuation in headers might be a matter of preference, but generally it is suggested not to use it
• Removing it also makes all headings consistent

v1.2.8

🚀 Enhancements

Use data source to retrieve health check IP ranges @kpocius (#88)

what

• Use google_netblock_ip_ranges data source to retrieve health check IP ranges

why

• This will ensure IP ranges are always up to date, and don't have to be manually updated if it changes on GCP side

references

• google_netblock_ip_ranges terraform data source

v1.2.7

🚀 Enhancements

Fix module idempotency by setting sample_rate on backend service log_config @kpocius (#89)

what

Set sample_rate to 1 (default value) on google_compute_backend_service resource log_config block

why

When used as-is, the module is not idempotent, and results in change on each apply:

Terraform will perform the following actions:

  # module.atlantis.google_compute_backend_service.default will be updated in-place
  ~ resource "google_compute_backend_service" "default" {
        id                              = "projects/argyle-security-admin/global/backendServices/atlantis"
        name                            = "atlantis"
        # (16 unchanged attributes hidden)

      ~ log_config {
          - sample_rate = 1 -> null
            # (1 unchanged attribute hidden)
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

references

google_compute_backend_service sample_rate documentation

The ideal solution would be to provide an input variable for setting both logging and its sample rate. Maybe it can be handled in a separate feature. Meanwhile this is a quick workaround which doesn't change the current behavior and makes the module idempotent.

v1.2.6

• No changes

v1.2.5

🚀 Enhancements

Pin the hashicorp/random provider @bschaatsbergen (#85)

what

• Pinned the hashicorp/random provider

v1.2.3

Rephrase "Example Usage' section @bschaatsbergen (#83)

what

*Rephrase the "Example Usage" section in the root README to be more transparent.

v1.2.2

Doc improvements @bschaatsbergen (#82)

what

• Moved some docs around and removed duplicated docs

why

• There was a lot of duplicated documentation

v1.2.1

🚀 Enhancements

Add cos image ID and managed SSL outputs @bschaatsbergen (#81)

what

• Added a few new outputs related to the COS image and managed SSL certificate.

why

• These could be useful to a user.

references

• Closes #39 .

v1.2.0

Introduce startup script var @bschaatsbergen (#80)

As proposed in #41, we should allow users to bring their own start-up script.

what

• Created a startup_script variable.

why

• Next to cloudinit, users should be able to execute their own startup script.

references

• Closes #41

v1.1.0

Add Identity-Aware Proxy support @bschaatsbergen (#78)

Closes #34

what

• Added a new variable iap, that's used to configure Identity-Aware Proxy on a new backend.
• If the iap var is set, we route everything but /events over the IAP protected backend.
• /events is excluded as it's used to handle inbound webhook requests.

why

• Users should be offered an alternative to the basic auth authentication provided by Atlantis.
• Preferably a Google Cloud native authentication service.

references

• https://cloud.google.com/iap