Hi everyone, its been a while since I wrote the last story. Been a new journey for me to actually able to work at Google (its my dream to be able to work here) and I do need to learn a lot so that I can actually contribute (everyone over here is totally super smart and super experienced!).

Its just a side exploration in between many other stuff I have poured upon my brain since the day 1 which touch the IaC on GCP. I found there are the native one through deployment manager and the other one through terraform (notes: there are so many other approaches which I have not yet explored, so I will focus on those two).

Cloud Deployment Manager | Google Cloud

Create and manage cloud resources with simple templates. View documentation for this product. Google Cloud Deployment…

cloud.google.com

I basically love the idea of IaC as we can now let the automation run instead of manual human intervention. Though the idea of automation is great, however the template/code/script required to be proper in the first hand. It is not as straightforward as UI console may provide in my opinion however once we have the artifact we are able to reuse as we see fit and that is very useful for quick changing environment or repetitive environment deployment (Eg. deploying dev, staging, and production).

Some thought on IaC:

  1. Once the deployment file are created we can re-use and with that reduce human error.
  2. Automation actually help to increase admin productivity as he/she can do other tasks while the automation is running.
  3. Deployment file and also the detail of deployment manager config are a great technical documentation (hitting two bird with one stone).
  4. The environment are properly managed, and we actually can do some planning phase (preview on Deployment Manager, or terraform plan).

#deployment-manager #cloud #iac #google #gcp #cloud

Infrastructure as Code — Exploring GCP Deployment Manager
1.05 GEEK