제공업체 문서에는 민감한 정보가 포함될 수 있는 구성 값이 표시됩니다. Google Cloud
예를 들어 리소스 google_storage_bucket_object를 사용하면 content 인수를 사용하여 Cloud Storage 객체를 만들 수 있습니다. 이 인수는 제공업체 문서의 google_storage_bucket_object 페이지에서 민감한 정보로 분류됩니다. Google Cloud
이러한 라벨을 사용하여 Terraform 구성을 만들 때 또는 사용하기 전에 기존 Terraform 구성을 검토할 때 유용한 정보를 얻을 수 있습니다.
클라우드 서비스의 제공 및 관리 중에 수집하거나 생성하는 개인 정보를 처리하는 방법에 관한 자세한 내용은 Google Cloud 개인정보처리방침을 참고하세요. Google Cloud
[[["이해하기 쉬움","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\u003eInfrastructure Manager uses Terraform configurations, referred to as "blueprints," to deploy resources and requires familiarity with Terraform.\u003c/p\u003e\n"],["\u003cp\u003eInfra Manager supports specific Terraform versions (1.2.3, 1.3.10, 1.4.7, 1.5.7), with the latest supported version being the default if none is specified.\u003c/p\u003e\n"],["\u003cp\u003eTerraform configurations for Infra Manager must adhere to constraints, including the provision of a valid Terraform root module and the avoidance of backend blocks.\u003c/p\u003e\n"],["\u003cp\u003eSensitive information should not be included in Terraform configuration values, as indicated by the Google Cloud provider documentation.\u003c/p\u003e\n"],["\u003cp\u003eWhen updating a deployment, you can only change to a later version of Terraform, you can't downgrade to an earlier supported version.\u003c/p\u003e\n"]]],[],null,["To work with Infrastructure Manager (Infra Manager), you should be\nfamiliar with Terraform. To learn more about\nTerraform, start with\n[What is Terraform?](https://developer.hashicorp.com/terraform/intro).\n\nInfra Manager deploys infrastructure resources and configurations that are\ndefined in a Terraform configuration. These configurations can consist\nof multiple files and directories but their entrypoint must be a\n[Terraform root module](https://developer.hashicorp.com/terraform/language/modules).\n\nInfra Manager uses the term *blueprint* to refer to a\nTerraform configuration.\n\nTo learn more about Terraform with Google Cloud, see\n[Terraform on Google Cloud](/docs/terraform).\n\nTerraform modules for Google Cloud\n\nFor a set of modules to provision Google Cloud resources, see\n[Terraform blueprints and modules for Google Cloud](/docs/terraform/blueprints/terraform-blueprints).\n\nYou can also create your own Terraform modules for Google Cloud. For more\ndetails, see\n[Creating Modules](https://developer.hashicorp.com/terraform/language/modules/develop).\n\nSupported Terraform versions\n\nInfra Manager supports the following Terraform versions:\n\n- Terraform version 1.2.3\n- Terraform version 1.3.10\n- Terraform version 1.4.7\n- Terraform version 1.5.7\n\nYou can use the flag `--tf-version-constraint` to specify the version of\nTerraform that Infra Manager uses to\n[create a deployment](/infrastructure-manager/docs/deploy-resources).\n\nIf you don't specify a version of Terraform, the latest support version\nis used by default.\n\nWhen updating a deployment, you can change the Terraform version to\na later version of Terraform. You cannot change to an earlier supported\nversion of Terraform.\n\nTo view the version of Terraform that was used to create a specific\ndeployment or revision, see\n[View details of a deployment](/infrastructure-manager/docs/view-deployments#deployment-details)\nand\n[View details of a revision](/infrastructure-manager/docs/view-deployments#revision-details).\n\nConstraints on Terraform configurations\n\nTo use Infrastructure Manager to deploy a Terraform configuration, the configuration\nhas the following constraints.\n\n- Don't include personal or sensitive information in Terraform configuration values. For more information, see the following section [Terraform configuration values and sensitive data](#config-values-data).\n- A valid [Terraform root module](https://developer.hashicorp.com/terraform/language/modules#the-root-module) must be provided. Templating or generation of Terraform is not supported.\n- The configuration should be actuatable by a [supported version of Terraform](#terraform_versions).\n- [Backend blocks](https://developer.hashicorp.com/terraform/language/backend) shouldn't be defined.\n- The use of [provisioners](https://developer.hashicorp.com/terraform/language/resources/provisioners/syntax) are not recommended. Use a different solution if possible. See [Provisioners are a Last Resort](https://developer.hashicorp.com/terraform/language/resources/provisioners/syntax#provisioners-are-a-last-resort) for more details about provisioners. If you are using provisioners, note that the [Infra Manager runtime environment](/infrastructure-manager/docs/overview#runtime_environment) can change at any time.\n\nTerraform configuration values and sensitive data\n\nDon't include personal or sensitive information in Terraform configuration\nvalues.\n\nThe [documentation for the Google Cloud provider](https://registry.terraform.io/providers/hashicorp/google/latest/docs) indicates configuration values that can potentially include\nsensitive information.\n\nFor example, the resource `google_storage_bucket_object` allows\ncreation of a Cloud Storage object using the `content` argument. This\nargument is labeled as sensitive on the\n[`google_storage_bucket_object` page of the Google Cloud Provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/storage_bucket_object#content).\n\nYou can use these labels to help guide you as you create Terraform\nconfigurations or as you review an existing Terraform configuration before use.\n\nSee the [Google Cloud Privacy Notice](/terms/cloud-privacy-notice) for\ninformation on how Google Cloud processes personal information it collects\nor generates during the provision and administration of the Cloud Services.\n\nUse the Terraform provider for Google Cloud\n\nYou can configure deployments and previews to use Infra Manager\nmaintained Terraform providers for Google Cloud.\n\nThis optional field lets you specify the use of the Infra Manager maintained Terraform\nproviders to create or update a deployment or preview deployment.\nYou can specify a Terraform provider using gcloud CLI.\n\nInfra Manager supports Terraform providers for Google Cloud:\n\n- `google`\n- `google-beta`\n\nOmit this field to use the [HashiCorp-maintained Terraform provider for Google Cloud](https://registry.terraform.io/providers/hashicorp/google/latest/docs).\n\nTo learn how to specify the use of a Infra Manager maintained Terraform provider,\nsee [Deploy infrastructure using Infrastructure Manager](/infrastructure-manager/docs/deploy-resources#storage-bucket),\n[Update a deployment](/infrastructure-manager/docs/update-deployment#storage-bucket), or\n[Preview a deployment](/infrastructure-manager/docs/preview-deployment#storage-bucket).\n\nCheck supported versions of the provider\n\nTo check the versions of a Terraform provider for Google Cloud that\nInfra Manager supports, you'll need to view the\n`manifest.json` in the Infra Manager maintained Cloud Storage bucket\n*associated with the region of your deployment* in the format: \n\n https://storage.googleapis.com/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e-im-providers/hashicorp/\u003cvar translate=\"no\"\u003ePROVIDER_VERSION\u003c/var\u003e/manifest.json\n\nYou can find a complete list of supported\nversions within the `versions` field of the `manifest.json` file.\n\nFor example, if your deployment is located in the `africa-south1` region and\nyou are using the `google-beta` provider, navigate to\n\u003chttps://storage.googleapis.com/africa-south1-im-providers/hashicorp/google-beta/manifest.json\u003e\nto view available regions.\n\nWhat's next\n\n- Learn more about [Infrastructure Manager](/infrastructure-manager/docs/overview).\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)."]]
