Create a reusable template from a running application
Stay organized with collections
Save and categorize content based on your preferences.
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:
Open your app-enabled folder or host project, depending on your
setup model.
Identify and review the source application
Use App Hub to get a clear blueprint of the existing application's
architecture:
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.
In the list of applications, find and select the running application you
want to use as a model.
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:
Design an application template,
mapping the inventory of services and workloads from your source
application onto the design canvas.
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.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-10 UTC."],[],[],null,["When an App Hub application is already running successfully, you can\ncreate a reusable template from it. This practice lets developer teams\nself-serve their deployments in a way that is consistent and compliant with your\norganization's standards.\n\nThis guide shows you how to standardize the architecture of an existing,\nregistered App Hub application by creating a governed, reusable\ntemplate.\n\nThis workflow is suitable for promoting best practices and supporting a\nconsistent and secure deployment of services. For example, use the architecture\nof a running `translator_v4.0` application to create a template for an upcoming\n`translator_v5.0` application.\n\nBefore you begin\n\nYou must complete the following steps before creating templates from existing\napplications:\n\n- **For administrators**:\n\n 1. [Set up Application Design Center](/application-design-center/docs/setup). You must configure Application Design Center to let users create application templates.\n 2. [Grant access to users](/resource-manager/docs/manage-applications#assign-roles). Assign appropriate IAM roles based on user's responsibilities in the application lifecycle.\n- **For developers and operators**:\n\n 1. Confirm with your administrator that the initial setup is finalized.\n 2. [Make sure you have the necessary IAM roles](/resource-manager/docs/manage-applications#assign-roles) for the tasks you want to perform.\n 3. Open your app-enabled folder or host project, depending on your [setup model](/app-hub/docs/set-up-app-hub).\n\nIdentify and review the source application\n\nUse App Hub to get a clear blueprint of the existing application's\narchitecture:\n\n1. 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](/app-hub/docs/set-up-app-hub).\n2. Navigate to the **Applications** page from App Hub:\n\n\n [Go to Applications](https://console.cloud.google.com/apphub/applications)\n\n \u003cbr /\u003e\n\n3. In the list of applications, find and select the running application you\n want to use as a model.\n\n4. In the application details page, review its registered services and\n workloads. This view serves as the source of truth for the application's\n architecture.\n\nGenerate and parametrize the template\n\nWith the application blueprint from App Hub, build a flexible, reusable\ntemplate in Application Design Center:\n\n1. [Design an application template](/application-design-center/docs/design-application-templates), mapping the inventory of services and workloads from your source application onto the design canvas.\n2. 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.\n3. Add a detailed description, version number, and other relevant metadata to the template.\n\nPublish and validate the template\n\nWhen you finish designing and parametrizing the template, publish it to a\ncatalog to make it available to other teams:\n\n1. [Verify your template](/application-design-center/docs/design-application-templates#verify_your_template).\n2. [Share the template to a catalog](/application-design-center/docs/design-application-templates#share-template-to-catalog).\n3. As a final validation, verify that the architecture of a test application matches the original [source application](#identify-application).\n\nDevelopers can now reuse the template for applications that are consistent and\ncompliant with your organization's standards."]]