terraform-example-foundation VS semantic-release

- How do we secure?

You can use this approach for each step along the way, how to secure secrets in your cloud? code? IaC? container deployments? CI/CD?

If we assume infra / app is code, the tooling matters a lot less. How do you provision certificates via IaC? How do you grant IAM to resources and how do you revoke?

There are examples like https://github.com/terraform-google-modules/terraform-exampl... of more advanced IaC architectures, but you can start as small or as complex as you want and evolve if done properly.

Personally, I love me some Kubernetes + ArgoCD (GitOps) + Google Workload Identity + Google Secret Manager, but I am 100% biased.

Also looked for something similar, and unfortunately didnt find one. Based our enterprise repo off the caf model (not using the module) similar to this google repo: https://github.com/terraform-google-modules/terraform-example-foundation

How did I tackle this exam? 1. On github there is an example foundation for GCP on terraform. https://github.com/terraform-google-modules/terraform-example-foundation I went through this week after week to help me learn. I made customizations and I deployed and destroyed over and over again, making changes. I used this to create a basic organization with a website, this is how I learnt.

If you are looking to setup a new cloud project with Terraform, then that is an another thing. For GCP, Google offers a toolkit: https://github.com/terraform-google-modules/terraform-example-foundation

https://github.com/terraform-google-modules/terraform-example-foundation maybe have a look at the layer approach from Google?

Auto-tagging a project, Renovate or Dependabot can do this. With a Git Workflow and another tool like semantic-release you can do this. This behavior is a “gymnastic” to do on the CI/CD of your project but it’s not complicated. For example with GitLab CI, you can verify the pipeline run on the default branch of your project :

I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.