Skip to content

Commit

Permalink
adding location and doc schema (#8371) (#477)
Browse files Browse the repository at this point in the history
* adding location and doc schema

* added copyright

* resolved required field, url_param_only field, description, autogen_async, async in Location

* resolved required field, url_param_only field, description, autogen_async, async in Location

* resolved hardcoded location, few fields in location, removed unnecessary enum values

* resolved project_number, added fields in location example

* DocumentSchema final changes

* added timeouts in Location

* adding missing fields from test report

* added DocumentSchema tests

* removed required field from processorType

* changed dummy_values

* removed fields under properties

* added new line

* added enum tests

* separated tests into separate files

* made Document Schema immutable

Signed-off-by: Modular Magician <[email protected]>
  • Loading branch information
modular-magician authored Jul 28, 2023
1 parent 052cdc2 commit b49d33c
Show file tree
Hide file tree
Showing 40 changed files with 1,285 additions and 0 deletions.
15 changes: 15 additions & 0 deletions document_ai_warehouse_document_schema_datetime/backing_file.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# This file has some scaffolding to make sure that names are unique and that
# a region and zone are selected when you try to create your Terraform resources.

locals {
name_suffix = "${random_pet.suffix.id}"
}

resource "random_pet" "suffix" {
length = 2
}

provider "google" {
region = "us-central1"
zone = "us-central1-c"
}
24 changes: 24 additions & 0 deletions document_ai_warehouse_document_schema_datetime/main.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
resource "google_document_ai_warehouse_document_schema" "example_datetime" {
project_number = data.google_project.project.number
display_name = "test-property-date_time"
location = "us"

property_definitions {
name = "prop7"
display_name = "propdisp7"
is_repeatable = false
is_filterable = true
is_searchable = true
is_metadata = false
is_required = false
retrieval_importance = "HIGHEST"
schema_sources {
name = "dummy_source"
processor_type = "dummy_processor"
}
date_time_type_options {}
}
}

data "google_project" "project" {
}
7 changes: 7 additions & 0 deletions document_ai_warehouse_document_schema_datetime/motd
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
===

These examples use real resources that will be billed to the
Google Cloud Platform project you use - so make sure that you
run "terraform destroy" before quitting!

===
79 changes: 79 additions & 0 deletions document_ai_warehouse_document_schema_datetime/tutorial.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# Document Ai Warehouse Document Schema Datetime - Terraform

## Setup

<walkthrough-author name="[email protected]" analyticsId="UA-125550242-1" tutorialName="document_ai_warehouse_document_schema_datetime" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>

Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.

<walkthrough-project-billing-setup></walkthrough-project-billing-setup>

Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.

## Terraforming!

Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
the project name from the environment variable.

```bash
export GOOGLE_CLOUD_PROJECT={{project-id}}
```

After that, let's get Terraform started. Run the following to pull in the providers.

```bash
terraform init
```

With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!

```bash
terraform apply
```

Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.

```bash
yes
```


## Post-Apply

### Editing your config

Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.

```bash
terraform plan
```

So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
run a 'plan' again.

```bash
terraform plan
```

Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
at the 'yes' prompt.

```bash
terraform apply
```

```bash
yes
```

## Cleanup

Run the following to remove the resources Terraform provisioned:

```bash
terraform destroy
```
```bash
yes
```
15 changes: 15 additions & 0 deletions document_ai_warehouse_document_schema_enum/backing_file.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# This file has some scaffolding to make sure that names are unique and that
# a region and zone are selected when you try to create your Terraform resources.

locals {
name_suffix = "${random_pet.suffix.id}"
}

resource "random_pet" "suffix" {
length = 2
}

provider "google" {
region = "us-central1"
zone = "us-central1-c"
}
31 changes: 31 additions & 0 deletions document_ai_warehouse_document_schema_enum/main.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
resource "google_document_ai_warehouse_document_schema" "example_enum" {
project_number = data.google_project.project.number
display_name = "test-property-enum"
location = "us"

property_definitions {
name = "prop6"
display_name = "propdisp6"
is_repeatable = false
is_filterable = true
is_searchable = true
is_metadata = false
is_required = false
retrieval_importance = "HIGHEST"
schema_sources {
name = "dummy_source"
processor_type = "dummy_processor"
}
enum_type_options {
possible_values = [
"M",
"F",
"X"
]
validation_check_disabled = false
}
}
}

data "google_project" "project" {
}
7 changes: 7 additions & 0 deletions document_ai_warehouse_document_schema_enum/motd
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
===

These examples use real resources that will be billed to the
Google Cloud Platform project you use - so make sure that you
run "terraform destroy" before quitting!

===
79 changes: 79 additions & 0 deletions document_ai_warehouse_document_schema_enum/tutorial.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# Document Ai Warehouse Document Schema Enum - Terraform

## Setup

<walkthrough-author name="[email protected]" analyticsId="UA-125550242-1" tutorialName="document_ai_warehouse_document_schema_enum" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>

Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.

<walkthrough-project-billing-setup></walkthrough-project-billing-setup>

Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.

## Terraforming!

Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
the project name from the environment variable.

```bash
export GOOGLE_CLOUD_PROJECT={{project-id}}
```

After that, let's get Terraform started. Run the following to pull in the providers.

```bash
terraform init
```

With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!

```bash
terraform apply
```

Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.

```bash
yes
```


## Post-Apply

### Editing your config

Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.

```bash
terraform plan
```

So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
run a 'plan' again.

```bash
terraform plan
```

Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
at the 'yes' prompt.

```bash
terraform apply
```

```bash
yes
```

## Cleanup

Run the following to remove the resources Terraform provisioned:

```bash
terraform destroy
```
```bash
yes
```
15 changes: 15 additions & 0 deletions document_ai_warehouse_document_schema_float/backing_file.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# This file has some scaffolding to make sure that names are unique and that
# a region and zone are selected when you try to create your Terraform resources.

locals {
name_suffix = "${random_pet.suffix.id}"
}

resource "random_pet" "suffix" {
length = 2
}

provider "google" {
region = "us-central1"
zone = "us-central1-c"
}
23 changes: 23 additions & 0 deletions document_ai_warehouse_document_schema_float/main.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
resource "google_document_ai_warehouse_document_schema" "example_float" {
project_number = data.google_project.project.number
display_name = "test-property-float"
location = "us"

property_definitions {
name = "prop2"
display_name = "propdisp2"
is_repeatable = false
is_filterable = true
is_searchable = true
is_metadata = false
is_required = false
retrieval_importance = "HIGHEST"
schema_sources {
name = "dummy_source"
processor_type = "dummy_processor"
}
float_type_options {}
}
}
data "google_project" "project" {
}
7 changes: 7 additions & 0 deletions document_ai_warehouse_document_schema_float/motd
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
===

These examples use real resources that will be billed to the
Google Cloud Platform project you use - so make sure that you
run "terraform destroy" before quitting!

===
79 changes: 79 additions & 0 deletions document_ai_warehouse_document_schema_float/tutorial.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# Document Ai Warehouse Document Schema Float - Terraform

## Setup

<walkthrough-author name="[email protected]" analyticsId="UA-125550242-1" tutorialName="document_ai_warehouse_document_schema_float" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>

Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.

<walkthrough-project-billing-setup></walkthrough-project-billing-setup>

Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.

## Terraforming!

Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
the project name from the environment variable.

```bash
export GOOGLE_CLOUD_PROJECT={{project-id}}
```

After that, let's get Terraform started. Run the following to pull in the providers.

```bash
terraform init
```

With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!

```bash
terraform apply
```

Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.

```bash
yes
```


## Post-Apply

### Editing your config

Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.

```bash
terraform plan
```

So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
run a 'plan' again.

```bash
terraform plan
```

Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
at the 'yes' prompt.

```bash
terraform apply
```

```bash
yes
```

## Cleanup

Run the following to remove the resources Terraform provisioned:

```bash
terraform destroy
```
```bash
yes
```
Loading

0 comments on commit b49d33c

Please sign in to comment.