search

terraform-google-modules / terraform-example-foundation

Shows how the CFT modules can be composed to build a secure cloud foundation
https://cloud.google.com/architecture/security-foundations
Apache License 2.0
1.18k stars 701 forks source link

chore(deps): update terraform googlecloudplatform/cloud-functions/google to v0.5.0 - autoclosed #1250

Closed renovate[bot] closed 1 month ago

renovate[bot] commented 1 month ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
GoogleCloudPlatform/cloud-functions/google (source) module minor 0.4.1 -> 0.5.0

Release Notes

GoogleCloudPlatform/terraform-google-cloud-functions (GoogleCloudPlatform/cloud-functions/google) ### [`v0.5.0`](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/blob/HEAD/CHANGELOG.md#050-2024-05-22) [Compare Source](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/compare/v0.4.1...v0.5.0) ##### ⚠ BREAKING CHANGES - **deps:** Update Terraform terraform-google-modules/cloud-storage/google to v6 ([#​123](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/123)) - **TPG>=5.12:** Update Terraform GoogleCloudPlatform/cloud-run/google to ~> 0.11.0 ([#​125](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/125)) - **deps:** Update Terraform terraform-google-modules/network/google to v9 ([#​99](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/99)) - **deps:** Update Terraform terraform-google-modules/pubsub/google to v6 ([#​100](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/100)) - **deps:** Update Terraform terraform-google-modules/cloud-storage/google to v5 ([#​98](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/98)) ##### Features - Add available_cpu to service_config ([#​65](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/65)) ([178cb1d](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/178cb1d4def363c3c6984bb5d854d7823a97e867)) - **deps:** Update Terraform Google Provider to >= 4.48, < 6 ([#​117](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/117)) ([8836a87](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/8836a8794d0d2934c3ddab2e64c14c87d3e90c4e)) - updated the role for CF Gen 2 ([#​88](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/88)) ([33e9efa](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/33e9efa1c2cea37cc64ea4f44aa6a4ce3568c259)) ##### Bug Fixes - **deps:** Allow Terraform Google Provider to v5 ([#​74](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/74)) ([38e7ed2](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/38e7ed2e3fb6770164f28259dbc62204ea2fd483)) - **deps:** Update Terraform GoogleCloudPlatform/cloud-run/google to ~> 0.10.0 ([#​96](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/96)) ([d06a9ad](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/d06a9ad5070e3daf29687d7accac990bb2b08352)) - **deps:** Update Terraform terraform-google-modules/cloud-storage/google to v5 ([#​98](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/98)) ([fb92c16](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/fb92c16dcec51a66a729e3446a2ba0401c8f73a7)) - **deps:** Update Terraform terraform-google-modules/cloud-storage/google to v6 ([#​123](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/123)) ([459c88f](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/459c88ff2348f6c5d0275d233c8b27f051d3b992)) - **deps:** Update Terraform terraform-google-modules/network/google to v9 ([#​99](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/99)) ([2188cec](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/2188cec9d754c442ccfadb8f54b77935173a99a3)) - **deps:** Update Terraform terraform-google-modules/pubsub/google to v6 ([#​100](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/100)) ([bc4fe56](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/bc4fe56900dd95e48f2b7a1236869db6e32a18f7)) - remove duplicate group_cloud_run_developer ([#​113](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/113)) ([69a64c0](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/69a64c0c96778f70f398d6a5eede0f4f4b2615ec)) - **TPG>=5.12:** Update Terraform GoogleCloudPlatform/cloud-run/google to ~> 0.11.0 ([#​125](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/issues/125)) ([0c64ca2](https://togithub.com/GoogleCloudPlatform/terraform-google-cloud-functions/commit/0c64ca2e9c2a2883f9e87131fa05b1ad298be08f))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Mend Renovate. View repository job log here.

dpebot commented 1 month ago

/gcbrun

apeabody commented 1 month ago

@eeaton - I forced the early creation of this PR, so no need to worry about the renovate/stability-days test.

eeaton commented 1 month ago

Ah looks like we were doing the same thing, I added the version bump to the existing PR: https://github.com/terraform-google-modules/terraform-example-foundation/pull/1221/commits/2287320706e09ca78a6afbba117e4f92b112c2fe

I think both get to the same outcome, but in terms of conventions, is it preferred to make a separate PR to fix the issue with the PR from renovate bot, or to modify the existing PR?

apeabody commented 1 month ago

Ah looks like we were doing the same thing, I added the version bump to the existing PR: 2287320

I think both get to the same outcome, but in terms of conventions, is it preferred to make a separate PR to fix the issue with the PR from renovate bot, or to modify the existing PR?

Either is fine, this will auto close if needed