Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini
berlaku untuk Apigee dan Apigee hybrid.
Deployment adalah entity hub API yang menjelaskan tempat API dihosting. Misalnya, deployment dapat mewakili proxy API Apigee, API yang di-deploy ke Google Cloud API Gateway, atau API yang di-deploy ke layanan Google Cloud lainnya atau layanan non-Google Cloud.
Anda dapat mengaitkan versi API dengan beberapa deployment untuk membuat model skenario seperti deployment pengembangan, staging, pengujian penerimaan pengguna (UAT), dan produksi yang sesuai dengan versi tertentu.
Anda juga dapat mengaitkan beberapa versi dengan deployment jika beberapa versi API (atau API yang berpotensi berbeda) di-deploy bersama.
Entitas deployment mencakup metadata seperti nama, nama tampilan, deskripsi, versi terkait, dan sebagainya. Tiga atribut berikut menentukan detail tentang API yang di-deploy dan
diperlukan untuk membuat deployment di API Hub:
Gambar 1. Entitas deployment mencakup jenis deployment, URI resource, dan URL endpoint.
Jenis deployment: Menentukan jenis deployment, seperti Apigee, Apigee Hybrid, Apigee Edge Private Cloud, dan lainnya.
URI Resource: URI ke resource deployment. Misalnya, jika resource deployment adalah proxy Apigee API, kolom ini harus menentukan URI ke antarmuka pengguna pengelolaan proxy.
Endpoint: Endpoint tempat deployment API yang sebenarnya memproses permintaan. Misalnya, kolom ini dapat berupa daftar alamat IP atau nama host.
Untuk mengetahui detail tentang cara membuat dan mengelola deployment, lihat Mengelola deployment.
[[["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-28 UTC."],[[["\u003cp\u003eThis content is applicable to both Apigee and Apigee hybrid platforms.\u003c/p\u003e\n"],["\u003cp\u003eA deployment, within the context of API Hub, defines where an API is hosted, and may represent various environments like dev, staging, or production.\u003c/p\u003e\n"],["\u003cp\u003eMultiple API versions can be associated with a single deployment, and a single version may have multiple deployments.\u003c/p\u003e\n"],["\u003cp\u003eCreating a deployment requires specifying its type, resource URI, and the endpoints it's listening on.\u003c/p\u003e\n"]]],[],null,["# Introduction to deployments\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\nA deployment is an API hub entity that describes where an API is hosted. For example,\na deployment could represent an Apigee API proxy, an API deployed to Google Cloud API\nGateway, or APIs deployed to other Google Cloud services or non-Google Cloud services.\n\nYou can associate an API version with multiple deployments to model scenarios such as dev,\nstaging, user acceptance testing (UAT), and production deployments corresponding to a\ngiven version.\n\nYou can also associate multiple versions with a deployment in cases where multiple\nversions of an API (or potentially different APIs) are deployed together.\n\nA deployment entity includes metadata such as name, display name, description, associated\nversions, and so on. The following three attributes specify details about the deployed API and\nare required to create a deployment in API hub:\n**Figure 1.** A deployment entity includes a deployment type, a resource URI, and endpoint URLs.\n\n- **Deployment type**: Specifies the type of deployment, such as Apigee, Apigee hybrid, Apigee Edge Private Cloud, and others.\n- **Resource URI** : A URI to the deployment resource. For example, if the deployment resource is an Apigee API proxy, then this field must specify the URI to the management user interface of the proxy. **Note:** For **Apigee** deployment types, we recommend that the Resource URI conforms to the following format: `organizations/([^/]+)/environments/([^/]+)/apis/([^/]+)$`\n |\n |\n | For example, the Resource URI for an Apigee API proxy deployed to the `prod`\n | environment of the `myorg` organization is\n | `organizations/myorg/environments/prod/apis/iloveapis`.\n- **Endpoints**: The endpoints on which the actual deployment of the API is listening to requests. For example, this field could be a list of IP addresses or hostnames.\n\nFor details on creating and managing deployments, see [Manage deployments](./manage-api-deployments)."]]
