배포는 API가 호스팅되는 위치를 설명하는 API 허브 항목입니다. 예를 들어 배포는 Apigee API 프록시, Google Cloud API 게이트웨이에 배포된 API 또는 다른 Google Cloud 서비스 또는 Google Cloud 이외의 서비스에 배포된 API를 나타낼 수 있습니다.
API 버전을 여러 배포와 연결하여 지정된 버전에 해당하는 개발, 스테이징, 사용자 수락 테스트(UAT), 프로덕션 배포와 같은 시나리오를 모델링할 수 있습니다.
여러 버전의 API(또는 잠재적으로 서로 다른 API)가 함께 배포되는 경우 여러 버전을 단일 배포에 연결할 수도 있습니다.
배포 항목에는 이름, 표시 이름, 설명, 관련 버전 등의 메타데이터가 포함됩니다. 다음 세 가지 속성은 배포된 API에 관한 세부정보를 지정하며 API 허브에서 배포를 만들 때 필요합니다.
[[["이해하기 쉬움","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-04(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)."]]
