Cloud Deployment Manager akan mencapai akhir dukungan pada 31 Desember 2025. Jika saat ini Anda menggunakan Deployment Manager, migrasikan ke Infrastructure Manager atau teknologi deployment alternatif paling lambat 31 Desember 2025 untuk memastikan layanan Anda berlanjut tanpa gangguan.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Konfigurasi menentukan struktur deployment Anda, termasuk jenis dan properti resource yang merupakan bagian dari deployment, template apa pun yang harus digunakan konfigurasi, dan subfile tambahan yang dapat dieksekusi untuk membuat konfigurasi akhir Anda. Anda harus selalu menentukan konfigurasi untuk membuat deployment.
Dalam konfigurasi, Anda dapat menentukan berbagai resource platform Google Cloud yang didukung dari berbagai layanan dalam satu file konfigurasi.
Beberapa contoh referensi meliputi:
Anda harus menulis file konfigurasi menggunakan sintaksis YAML. Untuk mempelajari
cara membuat file konfigurasi, lihat
Membuat Konfigurasi.
Bahasa template
Konfigurasi dapat mengimpor satu atau beberapa file template yang akan diperluas Deployment Manager selama deployment untuk membuat konfigurasi akhir. Anda dapat
menulis template dalam Jinja atau Python. Anda dapat menggabungkan
template. Satu konfigurasi dapat mengimpor template Jinja dan Python. Template dapat berupa file lokal atau file yang dihosting di URL pihak ketiga.
Template menawarkan fungsi tambahan, seperti kemampuan untuk menggunakan variabel lingkungan, kemampuan untuk menentukan variabel kustom, kemampuan untuk menggunakan library Python, dan sebagainya.
Semua konfigurasi diperluas di sisi server dalam lingkungan
terkontrol yang dikelola Deployment Manager. Untuk mencegah penyalahgunaan,
lingkungan ini dikelola dengan cermat oleh tim Deployment Manager
dan memiliki beberapa batasan:
Konfigurasi asli maupun konfigurasi yang diperluas tidak boleh melebihi 1 MB.
Setiap konfigurasi yang diupload ke Deployment Manager dibatasi dalam
jumlah waktu yang diperlukan konfigurasi untuk berjalan dan jumlah daya pemrosesan
yang digunakan konfigurasi selama perluasan. Jika Anda mengalami
batasan ini, pertimbangkan untuk membagi konfigurasi menjadi template yang lebih kecil,
atau menyederhanakan struktur kompleks seperti rekursi dan loop bertingkat.
Template Python apa pun yang Anda gunakan tidak dapat melakukan panggilan sistem atau jaringan. Template
ini akan otomatis ditolak.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[[["\u003cp\u003eA configuration file is mandatory for creating a deployment, defining the structure, resource types, properties, and templates involved.\u003c/p\u003e\n"],["\u003cp\u003eConfigurations support a wide array of Google Cloud resources, including Compute Engine, Kubernetes Engine, BigQuery, Cloud Storage, and Cloud SQL, all within a single file.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration files must be written using YAML syntax, and they can import templates for enhanced functionality using Jinja or Python.\u003c/p\u003e\n"],["\u003cp\u003eDeployment Manager expands configurations on the server-side, with limitations such as a 1 MB size limit for both original and expanded configurations.\u003c/p\u003e\n"],["\u003cp\u003ePython templates cannot make system or network calls, and exceeding time or power usage limits can require splitting or simplifying the configuration.\u003c/p\u003e\n"]]],[],null,["# Configurations Overview\n\nA configuration defines the structure of your deployment, including the\ntype and properties of the resources that are part of the deployment, any\ntemplates the configuration should use, and additional subfiles that can be\nexecuted to create your final configuration. You must always specify a\nconfiguration in order to create a deployment.\n\nIn your configuration, you can define a variety of supported Google Cloud\nplatform resources from different services in a single configuration file.\nSome example resources include:\n\n- All [Compute Engine](/compute/docs) resources including:\n - [Autoscaler](/compute/docs/autoscaler)\n - [Instance groups](/compute/docs/instance-groups) and [managed instance groups](/compute/docs/instance-groups/manager)\n- [Kubernetes Engine](/kubernetes-engine)\n- [BigQuery](/bigquery)\n- [Cloud Storage](/storage)\n- [Cloud SQL](/cloud-sql)\n\nFor a full list of resources, consult this table of\n[Supported resource types](/deployment-manager/docs/configuration/supported-resource-types)\nor make a\n[`list()`](/deployment-manager/docs/reference/latest/types/list) request to the\n[Types collection](/deployment-manager/docs/reference/latest/types).\n\nConfiguration language\n----------------------\n\nYou must write configuration files using\n[YAML](http://en.wikipedia.org/wiki/YAML) syntax. To learn\nhow to create a configuration file, see\n[Create a Configuration](/deployment-manager/docs/configuration/create-basic-configuration).\n\nTemplate languages\n------------------\n\nA configuration can import one or more template files that Deployment Manager\nwill expand during deployment to create the final configuration. You can\nwrite templates in either Jinja or Python. It is possible to mix and match\ntemplates. A single configuration can import both Jinja and Python templates. A\ntemplate can be a local file or a file hosted at a third-party URL.\n\nTemplates offer additional functionality, like the ability to use\nenvironment variables, the ability to define custom variables, the ability\nto use Python libraries, and so on.\n\nFor more information about templates, read\n[Creating a Basic Template](/deployment-manager/docs/configuration/templates/create-basic-template).\n\nConfiguration limits\n--------------------\n\nAll configurations are expanded on the server side within a controlled\nenvironment that Deployment Manager maintains. In order to prevent abuse,\nthis environment is closely managed by the Deployment Manager team\nand has some limitations:\n\n- Neither your original configuration nor your expanded configuration can exceed 1 MB.\n- Any configurations uploaded to Deployment Manager are limited in the amount of time the configuration can take to run and the amount of processing power the configuration consumes during expansion. If you run into this limitation, consider splitting your configuration into smaller templates, or simplify complex structures such as recursion and nested loops.\n- Any Python templates you use cannot make any system or network calls. These templates will automatically be rejected.\n\nWhat's next\n-----------\n\n- Create a [simple configuration](/deployment-manager/docs/configuration/create-basic-configuration).\n- Decide if you want to use [templates](/deployment-manager/docs/configuration/templates/create-basic-template).\n- If you are exposing your configuration to other users, consider [creating a schema](/deployment-manager/docs/configuration/templates/using-schemas).\n- Learn how you can [host templates externally](/deployment-manager/docs/configuration/templates/hosting-templates-externally)."]]
