Create a reusable template from a running application

Application Design Center lets you generate a reusable template from the architecture of a running App Hub application. Standardized templates help developer teams deploy applications consistently, support compliance with your organization's standards, and promote application management best practices.

You can use templates as the foundation for deployments to different environments or for development of new versions. For example, you can 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:

• For administrators:

  1. Choose your application setup model. Application Design Center requires a management project.
  2. Set up Application Design Center. You must configure Application Design Center to let users create application templates.
  3. Grant access to users. Assign appropriate IAM roles based on user's responsibilities in the application lifecycle.

• For developers and operators:

  1. Confirm with your administrator that the initial setup is finalized.
  2. Make sure you have the necessary IAM roles for the tasks you want to perform.
  3. Open your management project in the Google Cloud console.

Identify and review the source application

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

1. Navigate to the Applications page from App Hub:

   Go to Applications

2. In the list of applications, find the running application you want to use as a source model. Then, click its name.

3. 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 and maintain 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.