5-appinfra

5. Application Infrastructure pipeline

Purpose

The application infrastructure pipeline deploys the application-specific CI/CD resources as well as any additional application-specific services, such as databases or other managed services.

An overview of application inrastruction pipeline is shown below, in the context of deploying a new applicaiton across the Enterprise Application blueprint.

Application CI/CD pipeline

The application infrastructure pipeline creates the following resources to establish the application CI/CD pipeline, as defined in the cicd-pipeline submodule:

• Cloud Build trigger
• Artifact Registry repository
• Cloud Deploy pipeline and targets
• Cloud Storage buckets for build cache and other build artifacts
• Custom service accounts and IAM bindings

Other applicaiton infrastructure

The application infrastructure pipeline can create additional resources on a per-environment basis.

In this example, some services are using the alloydb-psc-setup submodule for creating an AlloyDB Cluster with Private Service Connect.

You may add additional infrastructure like application-specifc databases or other managed services by creating and invoking new submodules.

Usage

Running Terraform locally

1. The next instructions assume that you are in the terraform-google-enterprise-application/5-appinfra folder.

   cd terraform-google-enterprise-application/5-appinfra

Under the apps folder are examples for each of the cymbal bank applications.

1. Change directory into any of these folders to deploy.

cd apps/accounts-userservice

1. Update the configuration with values for your environment.

Deploy the shared environment first, which contains the application CI/CD pipeline.

1. Run init and plan and review the output.

   terraform -chdir=./envs/shared init
   terraform -chdir=./envs/shared plan

2. Run apply shared.

   terraform -chdir=./envs/shared apply

You can now deploy each of your environments (e.g. production).

1. Run init and plan and review the output.

   terraform -chdir=./envs/production init
   terraform -chdir=./envs/production plan

2. Run apply production.

   terraform -chdir=./envs/production apply

If you receive any errors or made any changes to the Terraform config or terraform.tfvars, re-run terraform -chdir=./envs/production plan before you run terraform apply -chdir=./envs/production.