Converting composite types to supported templates

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

A composite type is one or more templates, configured to work together, that are added permanently to Deployment Manager. For an overview of composite types, and steps to create them, visit Adding a template as a composite type.

However, the composite types feature is currently deprecated, and will no longer be usable in new or updated deployments on February 22, 2022. Your deployment configurations are affected if they use resource types with the format type: PROJECT_ID/composite:TEMPLATE_NAME.

This page describes the steps to convert composite types to supported templates.

Separating your composite type into individual templates

To convert your composite type into supported templates, you can either manually create a single template that contains all of the elements of the composite type, or separate out the elements of your composite type into individual template files.

For more information on templates and creating templates, refer to Creating a basic template.

Moving and importing your template files

You must copy all individual template files to the same location as your deployment. To avoid naming conflicts, we recommend that you use a separate folder from the folder you used for your deployment configuration.

You must also ensure that your configuration file is set up to import the individual template file or files. For information about importing templates, visit Importing the template.

Replacing references to your composite type

Next, update your deployments to use your individual template or templates directly, instead of the previous composite type.

Find and replace all instances of composite type syntax, such as:

type: PROJECT_ID/composite:main-template

Replace the composite type syntax with a direct reference to a template, such as:

type: PATH_TO/main-template.jinja