2016-08-23 22:34:54 +02:00
|
|
|
---
|
|
|
|
layout: "google"
|
|
|
|
page_title: "Google: google_project"
|
|
|
|
sidebar_current: "docs-google-project"
|
|
|
|
description: |-
|
2017-02-18 23:48:50 +01:00
|
|
|
Allows management of a Google Cloud Platform project.
|
2016-08-23 22:34:54 +02:00
|
|
|
---
|
|
|
|
|
|
|
|
# google\_project
|
|
|
|
|
2016-11-23 07:55:40 +01:00
|
|
|
Allows creation and management of a Google Cloud Platform project and its
|
|
|
|
associated enabled services/APIs.
|
2016-08-23 22:34:54 +02:00
|
|
|
|
2016-11-23 07:55:40 +01:00
|
|
|
Projects created with this resource must be associated with an Organization.
|
2017-03-27 22:28:26 +02:00
|
|
|
See the [Organization documentation](https://cloud.google.com/resource-manager/docs/quickstarts) for more details.
|
2016-11-23 07:55:40 +01:00
|
|
|
|
|
|
|
The service account used to run Terraform when creating a `google_project`
|
|
|
|
resource must have `roles/resourcemanager.projectCreator`. See the
|
|
|
|
[Access Control for Organizations Using IAM](https://cloud.google.com/resource-manager/docs/access-control-org)
|
|
|
|
doc for more information.
|
2016-08-23 22:34:54 +02:00
|
|
|
|
2017-02-24 09:48:03 +01:00
|
|
|
Note that prior to 0.8.5, `google_project` functioned like a data source,
|
|
|
|
meaning any project referenced by it had to be created and managed outside
|
|
|
|
Terraform. As of 0.8.5, `google_project` functions like any other Terraform
|
|
|
|
resource, with Terraform creating and managing the project. To replicate the old
|
|
|
|
behavior, either:
|
|
|
|
|
|
|
|
* Use the project ID directly in whatever is referencing the project, using the
|
|
|
|
[google_project_iam_policy](/docs/providers/google/r/google_project_iam_policy.html)
|
|
|
|
to replace the old `policy_data` property.
|
|
|
|
* Use the [import](/docs/import/usage.html) functionality
|
|
|
|
to import your pre-existing project into Terraform, where it can be referenced and
|
|
|
|
used just like always, keeping in mind that Terraform will attempt to undo any changes
|
|
|
|
made outside Terraform.
|
|
|
|
|
|
|
|
~> It's important to note that any project resources that were added to your Terraform config
|
|
|
|
prior to 0.8.5 will continue to function as they always have, and will not be managed by
|
|
|
|
Terraform. Only newly added projects are affected.
|
|
|
|
|
2016-08-23 22:34:54 +02:00
|
|
|
## Example Usage
|
|
|
|
|
|
|
|
```js
|
2016-11-08 08:27:32 +01:00
|
|
|
resource "google_project" "my_project" {
|
2017-02-18 23:48:50 +01:00
|
|
|
project_id = "your-project-id"
|
|
|
|
org_id = "1234567"
|
|
|
|
services = ["compute_component", "storage-component-json.googleapis.com", "iam.googleapis.com"]
|
2016-08-23 22:34:54 +02:00
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
## Argument Reference
|
|
|
|
|
|
|
|
The following arguments are supported:
|
|
|
|
|
2016-11-23 07:55:40 +01:00
|
|
|
* `project_id` - (Optional) The project ID.
|
|
|
|
Changing this forces a new project to be created. If this attribute is not
|
|
|
|
set, `id` must be set. As `id` is deprecated, consider this attribute
|
|
|
|
required. If you are using `project_id` and creating a new project, the
|
|
|
|
`org_id` and `name` attributes are also required.
|
|
|
|
|
|
|
|
* `id` - (Deprecated) The project ID.
|
|
|
|
This attribute has unexpected behaviour and probably does not work
|
|
|
|
as users would expect; it has been deprecated, and will be removed in future
|
|
|
|
versions of Terraform. The `project_id` attribute should be used instead. See
|
|
|
|
[below](#id-field) for more information about its behaviour.
|
2016-08-23 22:34:54 +02:00
|
|
|
|
2016-11-23 07:55:40 +01:00
|
|
|
* `org_id` - (Optional) The numeric ID of the organization this project belongs to.
|
|
|
|
This is required if you are creating a new project.
|
|
|
|
Changing this forces a new project to be created.
|
2016-08-23 22:34:54 +02:00
|
|
|
|
2017-02-20 18:32:24 +01:00
|
|
|
* `billing_acount` - (Optional) The alphanumeric ID of the billing account this project
|
|
|
|
belongs to. The user or service account performing this operation with Terraform
|
|
|
|
must have Billing Account Administrator privileges (`roles/billing.admin`) in
|
|
|
|
the organization. See [Google Cloud Billing API Access Control](https://cloud.google.com/billing/v1/how-tos/access-control)
|
|
|
|
for more details.
|
|
|
|
|
2016-11-23 07:55:40 +01:00
|
|
|
* `name` - (Optional) The display name of the project.
|
|
|
|
This is required if you are creating a new project.
|
|
|
|
|
|
|
|
* `skip_delete` - (Optional) If true, the Terraform resource can be deleted
|
|
|
|
without deleting the Project via the Google API.
|
|
|
|
|
|
|
|
* `policy_data` - (Deprecated) The IAM policy associated with the project.
|
|
|
|
This argument is no longer supported, and will be removed in a future version
|
|
|
|
of Terraform. It should be replaced with a `google_project_iam_policy` resource.
|
2016-08-23 22:34:54 +02:00
|
|
|
|
|
|
|
## Attributes Reference
|
|
|
|
|
|
|
|
In addition to the arguments listed above, the following computed attributes are
|
|
|
|
exported:
|
|
|
|
|
|
|
|
* `number` - The numeric identifier of the project.
|
2016-11-23 07:55:40 +01:00
|
|
|
* `policy_etag` - (Deprecated) The etag of the project's IAM policy, used to
|
|
|
|
determine if the IAM policy has changed. Please use `google_project_iam_policy`'s
|
|
|
|
`etag` property instead; future versions of Terraform will remove the `policy_etag`
|
|
|
|
attribute
|
|
|
|
|
|
|
|
## ID Field
|
|
|
|
|
2017-02-24 09:48:03 +01:00
|
|
|
In versions of Terraform prior to 0.8.5, `google_project` resources used an `id` field in
|
2016-11-23 07:55:40 +01:00
|
|
|
config files to specify the project ID. Unfortunately, due to limitations in Terraform,
|
|
|
|
this field always looked empty to Terraform. Terraform fell back on using the project
|
|
|
|
the Google Cloud provider is configured with. If you're using the `id` field in your
|
|
|
|
configurations, know that it is being ignored, and its value will always be seen as the
|
|
|
|
ID of the project being used to authenticate Terraform's requests. You should move to the
|
|
|
|
`project_id` field as soon as possible.
|