feat: (IAC-1312) Update Dependencies to Resolve Security Warnings #203
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Updates 3rd party dependencies in this project to resolve security findings from our scanning tool. Consumers of the Dockerfile will automatically have these updated dependencies installed, and users who directly run this project on this host will need to update the dependencies themselves. A note in the release notes will be made about this.
Version Updates
Here is a summary of version updates as well as code changes that needed to be made as result of the update.
Binaries
Providers
hashicorp/google & hashicorp/google-beta
hashicorp/google
v5.12.0
when usinggoogle_service_networking_connection
in conjunction with CloudSQL instances in order to cleanly delete resources we need to setdeletion_policy = "ABANDON"
hashicorp/kubernetes
hashicorp/null
hashicorp/random
hashicorp/local
hashicorp/external
hashicorp/time
Modules
terraform-google-modules/kubernetes-engine/google//modules/private-cluster
deletion_protection
is set to true by default, need to set this to false so that we can destroy the cluster.GoogleCloudPlatform/sql-db/google//modules/postgresql
terraform-google-modules/service-accounts/google
terraform-google-modules/address/google
terraform-google-modules/cloud-nat/google
enable_endpoint_independent_mapping
now defaults to false, explicitly setting it to true to retain previous behavior.Note: Although the versions have been bumped up, there are no breaking changes. A user could still modify their infrastructure they created with viya4-iac-gcp:5.0.0 with this latest release provided that they update their deps with
terraform init -upgrade
(a note will be included in the release notes)Tests