Skip to content

5.8.0 - February 15, 2024
Compare
Choose a tag to compare
@jarpat jarpat released this 15 Feb 15:41
· 18 commits to main since this release
5.8.0
86c3dca
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Release Notes

Dependency Updates

As part of PR #203, the required binaries and Terraform providers/modules have been updated to resolve some security notices that were picked up by our scanning process. The Dockerfile has been updated so a newly built docker image from this release will include these updates automatically. If you are running this project without the use of the Docker image, it is advised to update your local binaries and Terraform providers/modules, following the steps below:

  • See this section in the README a list of binaries you will need to install on your host. The versions listed are what we recommend and tested with, however the versions we listed back in the 5.0.0 release in this same document will still be compatible.
  • For the Terraform providers and modules you will need to run terraform init --upgrade before running any terraform commands with the new code. Refer to the init documentation from HashiCorp.

Migration to viya4-iac-gcp:5.8.0

As part of PR #203, there has been updates to the Terraform modules and providers that introduced new variables around infrastructure deletion:

  • hashicorp/google 5.12.0
    • Which adds the ability to set the deletion_policy for the google_service_networking_connection resource, we set this to ABANDON as required when used in conjunction with CloudSQL instances
  • terraform-google-modules/kubernetes-engine/google//modules/private-cluster 29.0.0
    • Introduces a new variable deletion_protection which is set to true by default, we override this to false

NOTE:

  • If you are coming from a previous viya4-iac-gcp:5.x.x release and want to update your infrastructure, running terraform apply should work just as before and will add these new values.
  • If you are planning to delete infrastructure that was created with a previous viya4-iac-gcp:5.x.x release, it is advised to use the version that you created the infrastructure with to delete it, otherwise you will need to run terraform apply first to pull in the new variables around infrastructure deletion before running terraform destroy.

ENHANCEMENTS:

  • #203: feat: (IAC-1312) Update Dependencies to Resolve Security Warnings
Assets 2
Loading