복합 유형은 Deployment Manager에 영구적으로 추가되었고 함께 작동하도록 구성된 하나 이상의 템플릿입니다. 복합 유형의 개요와 만드는 방법을 알아보려면 템플릿을 복합 유형으로 추가를 참조하세요.
하지만 복합 유형 기능은 현재 지원 중단되었으며2022년 2월 22일의 신규 배포 또는 업데이트된 배포에서 더 이상 사용할 수 없습니다. type: PROJECT_ID/composite:TEMPLATE_NAME 형식으로 리소스 유형을 사용하면 배포 구성이 영향을 받습니다.
이 페이지에서는 복합 유형을 지원되는 템플릿으로 변환하는 단계를 설명합니다.
복합 유형을 개별 템플릿으로 분리
복합 유형을 지원되는 템플릿으로 변환하려면 복합 유형의 모든 요소를 포함하는 단일 템플릿을 직접 만들거나 복합 유형의 요소를 개별 템플릿 파일로 분리하면 됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[[["\u003cp\u003eComposite types, which are multiple templates configured to work together, are deprecated and will not be usable in new or updated deployments after February 22, 2022.\u003c/p\u003e\n"],["\u003cp\u003eTo convert composite types, you can either create a single template containing all elements or separate the elements into individual template files.\u003c/p\u003e\n"],["\u003cp\u003eTemplate files should be moved to the same location as the deployment, preferably in a separate folder to avoid naming conflicts, and the configuration file must be updated to import these files.\u003c/p\u003e\n"],["\u003cp\u003eDeployments need to be updated to directly use the individual template or templates instead of the composite type, replacing the composite type syntax with direct template references.\u003c/p\u003e\n"]]],[],null,["# Converting composite types to supported templates\n\nA composite type is one or more templates, configured to work together, that are\nadded permanently to Deployment Manager. For an overview of composite types,\nand steps to create them, visit\n[Adding a template as a composite type](/deployment-manager/docs/configuration/templates/create-composite-types).\n\nHowever,\n[the composite types feature is currently deprecated](/deployment-manager/docs/deprecations/composite-types),\nand will no longer be usable in new or updated deployments on **February 22,\n2022** . Your deployment configurations are affected if they use resource types\nwith the format\n`type: `\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e`/composite:`\u003cvar translate=\"no\"\u003eTEMPLATE_NAME\u003c/var\u003e.\n\nThis page describes the steps to convert composite types to supported templates.\n\nSeparating your composite type into individual templates\n========================================================\n\nTo convert your composite type into supported templates, you can either manually\ncreate a single template that contains all of the elements of the composite\ntype, or separate out the elements of your composite type into individual\ntemplate files.\n\nFor more information on templates and creating templates, refer to\n[Creating a basic template](/deployment-manager/docs/configuration/templates/create-basic-template).\n\nMoving and importing your template files\n========================================\n\nYou must copy all individual template files to the same location as your\ndeployment. To avoid naming conflicts, we recommend that you use a separate\nfolder from the folder you used for your deployment configuration.\n\nYou must also ensure that your configuration file is set up to import the\nindividual template file or files. For information about importing templates,\nvisit\n[Importing the template](/deployment-manager/docs/configuration/templates/create-basic-template#importing_the_template).\n\nReplacing references to your composite type\n===========================================\n\nNext, update your deployments to use your individual template or templates\ndirectly, instead of the previous composite type.\n\nFind and replace all instances of composite type syntax, such as: \n\n type: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e/composite:main-template\n\nReplace the composite type syntax with a direct reference to a template, such\nas: \n\n type: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePATH_TO\u003c/span\u003e\u003c/var\u003e/main-template.jinja"]]
