Create a reusable template from a running application

When an App Hub application is already running successfully, you can create a reusable template from it. This practice lets developer teams self-serve their deployments in a way that is consistent and compliant with your organization's standards.

This guide shows you how to standardize the architecture of an existing, registered App Hub application by creating a governed, reusable template.

This workflow is suitable for promoting best practices and supporting a consistent and secure deployment of services. For example, use the architecture of a running translator_v4.0 application to create a template for an upcoming translator_v5.0 application.

Before you begin

You must complete the following steps before creating templates from existing applications:

Identify and review the source application

Use App Hub to get a clear blueprint of the existing application's architecture:

  1. In the Google Cloud console, use the project picker to select your host project or the management project of the app-enabled folder, depending on your setup model.
  2. Navigate to the Applications page from App Hub:

    Go to Applications

  3. In the list of applications, find and select the running application you want to use as a model.

  4. In the application details page, review its registered services and workloads. This view serves as the source of truth for the application's architecture.

Generate and parametrize the template

With the application blueprint from App Hub, build a flexible, reusable template in Application Design Center:

  1. Design an application template, mapping the inventory of services and workloads from your source application onto the design canvas.
  2. Identify any configuration values within the components that developers must customize for each deployment, such as region, machine sizes, or instance counts. Define these as input parameters in the template. This practice lets template users specify settings while maintaining the core architecture.
  3. Add a detailed description, version number, and other relevant metadata to the template.

Publish and validate the template

When you finish designing and parametrizing the template, publish it to a catalog to make it available to other teams:

  1. Verify your template.
  2. Share the template to a catalog.
  3. As a final validation, verify that the architecture of a test application matches the original source application.

Developers can now reuse the template for applications that are consistent and compliant with your organization's standards.