chore(master): release 4.1.0

[release-please]

🤖 I have created a release beep boop

4.1.0 (2024-08-01)

Features

• Add Billing Account Log sinks (#1164) (a72d12f)
• Create project destination and remove log bucket destination for the centralized logging (#1148) (0a03623)

Bug Fixes

• #1229 - fix 3-nhas symlinks (#1230) (05a2308)
• Add roles and service enablements to bootstrap project (#1175) (a759ee9)
• bump terraform base version from 1.3.0 to 1.3.10 (#1253) (a97d2b4)
• bump terraform version from 1.3.10 to 1.5.7 (#1268) (77827b2)
• cai: modules must not define providers (#1132) (f396741)
• deps: bump debug from 4.1.1 to 4.3.4 in /1-org/modules/cai-monitoring/function-source (#1048) (145c433)
• deps: relax to terraform google v5 (#1066) (a6adc7e)
• deps: update dependency @google-cloud/security-center to v8.8.0 (#1123) (299f10c)
• deps: update dependency moment to v2.30.1 (#1068) (05acc75)
• deps: update GO 1.21 (#1057) (e96ab70)
• deps: update GO modules (#1077) (2d9a438)
• deps: Update golangci/golangci-lint-action action to v4 (#1114) (ba6b860)
• deps: update module github.com/hashicorp/hcl/v2 to v2.21.0 (#1279) (822cc42)
• deps: Update Terraform terraform-google-modules/bootstrap/google to v7 (#1093) (16bd67c)
• deps: update terraform terraform-google-modules/cloud-router/google to v6 (#1089) (cb5b516)
• deps: update terraform terraform-google-modules/cloud-storage/google to v5 (#1088) (5c737b0)
• deps: update terraform terraform-google-modules/kubernetes-engine/google to v29 (#1094) (0f79a88)
• deps: Update Terraform terraform-google-modules/kubernetes-engine/google to v30 (#1108) (66ea687)
• deps: update terraform terraform-google-modules/kubernetes-engine/google to v31 (#1260) (01ed7d0)
• deps: update terraform terraform-google-modules/log-export/google to v8 (#1171) (a63dc88)
• deps: Update Terraform terraform-google-modules/network/google to v9 (#1095) (fdba866)
• deps: update terraform terraform-google-modules/pubsub/google to v6 (#1096) (3a92c9a)
• deps: update terraform terraform-google-modules/vm/google to v10 (#1097) (8a0e477)
• deps: update terraform terraform-google-modules/vpc-service-controls/google to v5 (#1098) (b1be0d5)
• deps: Update Terraform terraform-google-modules/vpn/google to v4 (#1100) (2c4a27b)
• deps: update terraform-google-modules/network/google to v8.0 (#1082) (6d8e106)
• deps: update tf modules (#1023) (03b1976)
• deps: update to terraform-google-modules/network/google//modules/network-peering v8 for increased TPG v5 compatibility (#1073) (5d808b1)
• docs: Update 3-networks-dual-svpc README after accidental change (#1294) (57c96c4)
• Fix of the new group structure (#1174) (dd6c09c)
• Fix project labels (#1107) (eb28ecb)
• Groups creation and permissions (#1110) (f57a47c)
• module seed_bootstrap now waiting on module required_groups (#1273) (ceeead2)
• provider: perma-diff in provider causes Cloud Functions in 1-org to always fail (#1311) (4a92a09)
• removed duplicate folder in README segment 5. app-infra (#1244) (229e53c)
• tfvars: fix broken symlinks (#1196) (5e11853)
• update project-factory version in CI/CD projects (#1255) (e23f95e)
• use bootstrap.outputs.common_config as default region (#1181) (105fe52)
• vars: remove additional variables leftover from env monitoring project (#1281) (55b06bf)
• VPCSC: enable dryrun mode (#1210) (4365eab)

---

This PR was generated with Release Please. See documentation.

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[kkrastev-cloudoffice]

yo is 5.0.0 coming out?

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[eeaton]

Hi @kkrastev-cloudoffice, this project uses the release-please bot for tagging major versions, but we're not doing automatic version tag upgrades because we have some waterfall dependencies across other assets. Major architectural changes need coordination with a rewrite of the guide and other assets. There are some significant architectural fixes we'll make in the coming months as part of v5 overhaul, then release a formal v5 tag once those are available.

For practical use, the delayed release of version tags shouldn't impact your use because all hotfixes and QOL improvements since v4.0 version in december are available publicly on the main branch. See also intended usage and support: the expectation with this repo is that it will be cloned and forked to your own version, not used as a remote reference, so the tags don't have the intended use of pinning remote versions.

Open to feedback if this approach doesn't work for your use case.

[kkrastev-cloudoffice]

Hi @eeaton I am trying to create a custom LZ for our purposes, based on 4.0.0 and I am having the following issue. I want to deploy locally with terraform and use cloudbuild later. Reading from the dox for 0-bootstrap, it says:

Deploying with Cloud Build
Warning: This method has a dependency on Cloud Source Repositories, which is no longer available to new customers. If you have previously used the CSR API in your organization then you can use this method, but a newly created organization will not be able to enable CSR and cannot use this deployment method. In that case, we recommend that you follow the directions for deploying locally, Github, Gitlab, or Terraform Cloud instead.

Where are the local instructions? https://github.com/terraform-google-modules/terraform-example-foundation/blob/master/0-bootstrap/README.md#running-terraform-locally

I see nothing here and can't really continue. Currently I don't see how to proceed using this module with cloudbuild or locally.

I guess this will be fixed in 5.0.0. I am thinking to just fork the 5.0.0 branch. What do you think?

Cheers,
Krasi

[eeaton]

@kkrastev-cloudoffice , thanks for sharing the context, I think I can help.

In this context, "running locally" means running terraform commands from your own workstation, without a remote source repository and without Cloud Build or similar CICD tools. The directions for running locally are contained in each stage. For example after deploying 0-bootstrap, then you would follow the directions in 1-org for running locally. The 0-bootstrap directions for Cloud Build are effectively also local, because at this stage you're running all the terraform commands from your local workstation until the repositories are set up. Go through the same directions related to terraform steps, and ignore step 13 onwards about configuring source repos. If you get an error about enabling the CSR API, remove the offending line from your cloud and try again.

It's fair feedback that this isn't clear from the bootstrap directions, I'll add this to the backlog in #1249 to rewrite the default deployment options and guidance.

Btw, re: forking the 5.0.0 branch...
The only difference between the branch in this PR that release bot is preparing and the master branch at head is that this 5.0 branch adds a release tag.

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[eeaton]

We will now make an exception and release a tagged version 4.1.0 based on an internal development use case that needs to pin directions to a known good version and needs some of the fixes introduced in this PR.

Going forward, hotfixes and support issues will continue to be merged to main branch and will be available without a tag update. We have some waterfall planning and dependencies for making more significant architectural changes that will be released as v5 next quarter.

It is still the intent that users of this blueprint fork it and use it from their own repo, we do not intend to support using this repo as a remote reference (see intended usage and support).

[release-please]

🤖 Created releases:

• v4.1.0
  🌻