Including a template in your application

You will recall from the previous chapters that we had several templates for different tiers. We had core (network and security), web (frontend), middleware (backend), and database tiers.

So far, we haven't stored our templates in the version control system, but since we need to apply Continuous Delivery, we need to figure out the proper way to store them. Normally, it all depends on how you want to organize your workflow. If you have a separate operations or cloud team that is responsible for infrastructure and operations, it is wise to keep all the templates in a single repository. Developers will then supply you with any desired changes to the infrastructure or with the new version of the application.

Our flow is as follows:

1. The developer publishes a new version of an app.
2. The developer provides the operations team with the new version and/or changes.
3. The operations team makes changes to parameters and/or templates...