Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/application-design-center/docs/design-application-templates below:

Design application templates | Application Design Center

Stay organized with collections Save and categorize content based on your preferences.

Preview

This product is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products are available "as is" and might have limited support. For more information, see the launch stage descriptions.

Administrators create application templates to help ensure that their preferred architecture is used by each development team. This helps you govern the resources and configurations that developers use in their application deployments.

Once you create an application template, it is available to others in your space. You can also add a template to a catalog to share with other spaces.

Developers can use your template to create and deploy an application. When developers create an application, they can configure each component from the template, but they can't add or remove any components. The template generates Terraform code, which developers can download or deploy from App Design Center.

This document helps you design, configure, and share an application template using App Design Center.

You must have one of the following roles:

• Application Design Center Admin (roles/designcenter.admin)
• Application Design Center User (roles/designcenter.user)

Create application templates to share your architecture design with development teams. You can add the following components to your template design:

• Assets: High-level resources that help you control other resources. For example, service accounts.

• Services: Network or API interfaces that are consumed over the network. Examples include Cloud Storage and Vertex AI.

• Workloads: Binary deployments that perform business functions. Examples include Cloud Run and Compute Engine.

As you design your template, Terraform code is generated to reflect the design and configuration details.

Template details help you categorize your template and help developers decide whether to use your template.

To enter details for your template, do the following:

1. From the navigation menu, click Templates.

   Go to Templates

2. Click Create template.

3. In the Template name field, enter a unique identifier for the template. This field is required.

4. In the Display name field, enter an identifier to display in the Google Cloud console.

5. In the Description field, enter a brief explanation of the application's purpose.

6. Click Create template. The design canvas is displayed.

You can design your template by adding components to the following starting points:

• A blank canvas.
• A Google-provided template.
• A template that you generate with Gemini assistance.

To design your template, do the following:

1. From the design canvas, make sure Design is selected.

2. Do one of the following to get started:

   • To start from scratch, from the Components area, click a component to add it to the canvas area.

   • To start from a Google-provided template, click the template name.

   • To use natural language chat to generate a template, click Custom Application with Gemini.

3. To create a communication channel between components, do one of the following:

   • To connect two components on the canvas, drag from a blue dot on a component to a blue dot on another component.

   • To add to an existing component, click add Add and select the component to add.

   For connection details, see the configuration documentation for each supported resource.

4. To remove a component or connection, do the following:

   1. In the canvas, click the component or connection.

   2. In the Configuration area, click Delete.

   3. In the field, enter delete.

   4. Click Delete.

For each asset, service or workload that you add to the canvas, you can specify configuration details such as name, project where the resource is created, and location.

All component configuration details are optional when you create the template. If you specify configuration details, they are used as default values for applications. Before developers deploy an application , they must configure the required details for each supported resource in the application.

To specify component configuration details as default values, do the following:

1. From the design canvas, click a component.

2. In the Configuration area, from the Project ID list, select the project where you want to deploy the resource. Select a project with the following qualifications:

   • The project must be a descendant of the selected app-enabled folder.
   • The project must not be a management project.

3. Configure additional settings for the resource. For example, for Cloud SQL, you might configure the following:

   • Region
   • Backup configuration
   • Database flags
   • IP configuration

   For links to configuration documentation for each component, see Supported resources.

4. Click Save.

As you design your application template, Terraform code is generated to reflect the design and configuration details. To view the Terraform code, do the following:

1. From the design canvas, click Code. Cloud Shell Editor opens and displays the generated Terraform files.

2. In the Explorer area, click main.tf. The Terraform module for each component is displayed.

If you no longer need a template, you can delete it.

1. From the design canvas, click more_vert Actions.
2. Click Delete.

Before you share your template with developers, make sure that it functions as you intended. To verify your template, do the following:

1. Create an application with the following settings:
   1. From the Environment list, select TEST.
   2. From the Criticality list, select LOW.
2. Deploy the application. For steps to deploy, see Deploy an application.
3. Test your infrastructure to make sure that it meets your requirements.
4. To avoid recurring costs, delete the test deployment.

Once you have verified your template, you can publish the template to a catalog. The template can be used by application developers who have access to a space where the catalog is shared.

1. From the design canvas, click Add to Catalog.
2. To manage spaces where the catalog is shared, see Manage catalogs.

As you gain experience with your application and your business needs evolve, you might want to update your application template. For example, you might decide to improve performance for a backend service by adding a Memorystore service for caching.

If you make changes to a template, those changes are not automatically published to the catalog. To share the latest revision, publish the template to the catalog again.

To create a new revision, do the following:

1. From the navigation menu, click Templates.

   Go to Templates

2. Select the application template that you want to revise. The canvas opens.

3. Modify the template to fit your new requirements. For example, add and configure a new component.

4. To share the latest revision with other spaces, add the template to relevant catalogs again.

• To share templates with other spaces, create and share a catalog.

• Before you deploy, create an application.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-02 UTC.

[[["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-07-02 UTC."],[[["Application templates help administrators ensure consistent architecture across development teams by governing resource and configuration usage in application deployments."],["Templates can be created from scratch or from Google-provided starting points, incorporating assets, services, and workloads, which then generate Terraform code."],["Application templates can be designed on a canvas, where components are added and connected, and configuration details are specified, with these settings acting as defaults for application instances."],["Templates must be verified by creating a test application instance, deploying it, and testing the infrastructure before sharing them with developers or publishing them to a catalog."],["Templates can be revised and re-shared, and changes will not be automatically updated, but can be re-shared by republishing them to the catalog."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4