Cloud Native Development with Google Cloud

Chapter 12. Factory

In previous chapters, you have been taking a largely manual approach to deploying both infrastructure and services. To be fair, leveraging the automation in the gcloud CLI and Cloud Run, in particular, has helped a lot, but it is still a manual process.

In Chapter 11, where you built the citadel (in particular, when configuring the API Gateway and Global HTTP Load Balancer), there was a lot of manual configuration and typing of commands. It was repetitive and error-prone, and if you wanted to deploy the application again, you would have to repeat the process.

Automating Build, Deployment, and Provisioning

This is a waste of time when you could be getting on with developing more features rather than fiddling with the command line. This type of work is known as “toil.” Toil is bad; toil should be eliminated when you see it. Toil is a sign that you need to automate something. When I first learned about software development at school, I was taught that when you have to do something more than twice, you should write a program to do it for you. This is one of those times that advice applies.

In this chapter, you will look at how you can use Google Cloud to automate away the toil you have been increasingly experiencing in previous chapters. You will also learn how this can be done for provisioning the infrastructure too.

Note

The code for this chapter is in the factory folder of the GitHub repository.

Requirements

You can think of what you are doing in this chapter ...