배포는 여러 위치 및 여러 프로젝트에 Google Cloud 리소스를 프로비저닝할 수 있습니다. 다음 사항을 참고하세요.
해당 위치에서 특정 리소스를 사용할 수 있어야 합니다. 예를 들어 Cloud Run이 제공되는 위치 목록은 Cloud Run 위치를 참고하세요.
서비스 계정에는 지정된 프로젝트에 배포하는 데 필요한 권한이 있어야 합니다. 자세한 내용은 서비스 계정 구성을 참고하세요.
배포 메타데이터
Infra Manager는 Infra Manager가 실행되는 프로젝트 및 위치에 스토리지 버킷을 만듭니다. 배포가 생성되면 Infrastructure Manager 아티팩트는 gs://PROJECT_NUMBER-LOCATION-blueprint-config라는 이름의 이 스토리지 버킷에 있습니다.
Infra Manager는 Terraform 구성을 나타내는 데 블루프린트라는 용어를 사용합니다.
여기서 다음을 바꿉니다.
PROJECT_ID: 인프라 관리자가 실행되는 프로젝트 ID입니다.
LOCATION: Infra Manager가 실행되는 위치입니다.
스토리지 버킷의 배포 아티팩트에는 다음이 포함됩니다.
Cloud Build 로그
Terraform 로그
Terraform 구성 사본
Infra Manager는 Terraform 상태 파일의 사본도 저장합니다. 파일 액세스를 비롯한 상태 파일에 관한 자세한 내용은 Terraform 상태 파일 관리를 참고하세요.
버전은 배포의 버전이므로 Infra Manager는 각 버전에 대해 이 배포 메타데이터를 저장합니다.
미리보기에는 특정 Terraform 구성을 실행하는 작업이 설명됩니다.
새 배포를 만들거나 배포를 업데이트하기 전에 배포를 미리 보고 프로비저닝할 리소스를 확인할 수 있습니다.
메타데이터 미리보기
Infra Manager는 Infra Manager가 실행되는 프로젝트 및 위치에 스토리지 버킷을 만듭니다. 미리보기가 생성되면 Infra Manager 아티팩트는 이름이 gs://PROJECT_NUMBER-LOCATION-blueprint-config인 이 저장소 버킷에 있습니다.
새 배포의 미리보기의 경우 메타데이터가 new-previews 접두사로 구성됩니다(예: gs://PROJECT_NUMBER-LOCATION-blueprint-config/new-previews/preview-name).
기존 배포의 업데이트를 미리 볼 수도 있습니다. 기존 배포를 타겟팅하는 이러한 미리보기의 경우 아티팩트가 배포 아티팩트와 동일한 스토리지 버킷에 저장됩니다. 이름이 gs://PROJECT_ID-LOCATION-blueprint-config/deployment-ID/previews/preview-ID인 스토리지 버킷
Infra Manager는 Terraform 구성을 나타내는 데 blueprint라는 용어를 사용합니다.
[[["이해하기 쉬움","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-05(UTC)"],[[["\u003cp\u003eInfra Manager uses deployments to provision Google Cloud resources to multiple locations and projects, with each deployment creating a storage bucket containing artifacts like Cloud Build and Terraform logs, and a copy of the Terraform configuration.\u003c/p\u003e\n"],["\u003cp\u003eDeployments and their revisions, which are versions of a deployment, have specific naming formats that include the project ID, location, and a user-specified identifier, with the revision ID being auto-incremented by Infra Manager.\u003c/p\u003e\n"],["\u003cp\u003ePreviews are used to describe and verify the actions to actuate a specific Terraform configuration before creating or updating a deployment, storing metadata in a designated storage bucket.\u003c/p\u003e\n"],["\u003cp\u003eThe Deployment ID and the Preview ID must contain only lowercase letters, numbers, or hyphens; start with a lowercase letter; end with a number or lowercase letter; and be unique within the project and location where the Infra Manager is run.\u003c/p\u003e\n"]]],[],null,["# Deployments, revisions, and previews overview\n\nThis page describes deployments and revisions, including the following:\n\n- List of metadata stored for each deployment.\n- The format of the deployment name and revision name.\n\nDeployments\n-----------\n\nInfra Manager provisions resources onto Google Cloud as a deployment.\n\nA deployment can provision Google Cloud resources to multiple locations and\nto multiple projects. Note that:\n\n- The specific resources need to be available in the locations. For example, see [Cloud Run locations](/run/docs/locations) for the list of locations where Cloud Run is available.\n- The service account must have the permissions that are required to deploy to the specified projects. For details, see [Configure the service account](/infrastructure-manager/docs/configure-service-account).\n\n### Deployment metadata\n\nInfra Manager creates a storage bucket in the project and location\nwhere Infra Manager is run. After the deployment is created, the\nInfrastructure Manager artifacts are in this storage bucket which has the name:\n`gs://`\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e`-blueprint-config`.\n\nInfra Manager uses the term *blueprint* to refer to a\nTerraform configuration.\n\nWhere you replace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the project ID where Infra Manager is run.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location where Infra Manager is run.\n\nThe deployment artifacts in the storage bucket include:\n\n- Cloud Build logs.\n- Terraform logs.\n- A copy of the Terraform configuration.\n\nInfra Manager also stores a copy of the Terraform state file. For\ndetails about the state file, including accessing the file, see\n[Manage the Terraform state file](/infrastructure-manager/docs/state-file).\n\nRevisions are versions of a deployment, so Infra Manager stores\nthis deployment metadata for each revision.\n\n### Deployment name\n\nThe format of the deployment name is: \n\n projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/deployments/\u003cvar translate=\"no\"\u003eDEPLOYMENT_ID\u003c/var\u003e\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is the project ID where Infra Manager runs.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e is the location where Infra Manager runs. See [Infrastructure Manager locations](/infrastructure-manager/docs/locations) for the list of valid locations.\n- \u003cvar translate=\"no\"\u003eDEPLOYMENT_ID\u003c/var\u003e is the deployment identifier, and is a user-specified name. This name must:\n - Contain only lowercase letters, numbers, or hyphens.\n - Start with a lowercase letter.\n - End with a number or lowercase letter\n - Cannot be the string `archived-deployments` or `archived-previews`\n - Must be unique within the project and location where Infra Manager is run.\n\nFor example: \n\n projects/my-project/locations/us-central1/deployments/my-deployment\n\nRevisions\n---------\n\nRevisions are versions of a deployment. When you initially create a\ndeployment, this deployment is also a revisions and has the revision ID `r-0`.\n\n### Revision name\n\nWhen you create an Infra Manager deployment, it is automatically given the\nrevision identifier `r-0`. If you update the deployment, then Infrastructure Manager\ncreates a new revision with identifier `r-1`. For every new revision,\nthe identifier increases by one. The revision identifier can only be set\nby Infrastructure Manager.\n\nFor example, a revision name could be: \n\n projects/my-project/locations/us-central1/deployments/my-deployment/revisions/r-1\n\nPreviews\n--------\n\nA preview describes the actions to actuate a specific Terraform configuration.\nBefore you create a new deployment or update a deployment, you can preview\nthe deployment to verify the resources that are planned to be provisioned.\n\n### Preview metadata\n\nInfra Manager creates a storage bucket in the project and location\nwhere Infra Manager is run. After the preview is created, the Infra Manager artifacts are in this storage bucket which has the name:\n`gs://`\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e`-blueprint-config`.\n\nFor a preview of a new deployment, the metadata is organized with a\n`new-previews` prefix, for example:\n`gs://`\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e`-blueprint-config/new-previews/preview-name`\n\nYou can also preview an update to an existing deployment. For these previews\ntargeting an existing deployment, the artifacts are stored in the same storage\nbucket as the deployment artifacts. The storage bucket which has the name:\n`gs://`\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e`-blueprint-config/deployment-ID/previews/preview-ID`.\n\nInfra Manager uses the term *blueprint* to refer to a Terraform configuration.\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: : the project ID where Infra Manager is run.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: : the location where Infra Manager is run.\n\nThe preview artifacts in the storage bucket include:\n\n- Cloud Build logs.\n- Terraform logs.\n- A copy of the Terraform configuration.\n\n### Preview name\n\nThe format of the preview name is: \n\n projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/previews/\u003cvar translate=\"no\"\u003ePREVIEW_ID\u003c/var\u003e\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is the project ID where Infra Manager runs.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e is the location where Infra Manager runs. See [Infrastructure Manager locations](/infrastructure-manager/docs/locations) for the list of valid locations.\n- \u003cvar translate=\"no\"\u003ePREVIEW_ID\u003c/var\u003e is the deployment identifier, and is a user-specified name. This name must:\n - Contain only lowercase letters, numbers, or hyphens.\n - Start with a lowercase letter.\n - End with a number or lowercase letter\n - Cannot be the string `archived-deployments` or `archived-previews`\n - Must be unique within the project and location where Infra Manager is run.\n\nFor example: \n\n projects/my-project/locations/us-central1/previews/my-preview\n\nWhat's next\n-----------\n\n- Learn more about [Terraform with Google Cloud](/docs/terraform).\n- [Create a deployment](/infrastructure-manager/docs/deploy-resources).\n- [Update a deployment](/infrastructure-manager/docs/update-deployment).\n- [View the state of a deployment](/infrastructure-manager/docs/view-deployments).\n- [Delete a deployment](/infrastructure-manager/docs/delete-deployments)."]]
