Skip to content

Commit

Permalink
Source versioning: Postgres, MySQL and Load generator (#647)
Browse files Browse the repository at this point in the history
  • Loading branch information
bobbyiliev authored Jan 3, 2025
1 parent e05f480 commit 9663cc4
Show file tree
Hide file tree
Showing 77 changed files with 6,905 additions and 89 deletions.
2 changes: 2 additions & 0 deletions compose.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ services:
- --system-parameter-default=max_clusters=100
- --system-parameter-default=max_sources=100
- --system-parameter-default=max_aws_privatelink_connections=10
- --system-parameter-default=enable_create_table_from_source=on
- --all-features
environment:
MZ_NO_TELEMETRY: 1
Expand Down Expand Up @@ -48,6 +49,7 @@ services:
- --system-parameter-default=max_sources=100
- --system-parameter-default=max_aws_privatelink_connections=10
- --system-parameter-default=transaction_isolation=serializable
- --system-parameter-default=enable_create_table_from_source=on
- --all-features
environment:
MZ_NO_TELEMETRY: 1
Expand Down
53 changes: 53 additions & 0 deletions docs/data-sources/source_reference.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
# generated by https://github.com/hashicorp/terraform-plugin-docs
page_title: "materialize_source_reference Data Source - terraform-provider-materialize"
subcategory: ""
description: |-
The materialize_source_reference data source retrieves a list of available upstream references for a given Materialize source. These references represent potential tables that can be created based on the source, but they do not necessarily indicate references the source is already ingesting. This allows users to see all upstream data that could be materialized into tables.
---

# materialize_source_reference (Data Source)

The `materialize_source_reference` data source retrieves a list of *available* upstream references for a given Materialize source. These references represent potential tables that can be created based on the source, but they do not necessarily indicate references the source is already ingesting. This allows users to see all upstream data that could be materialized into tables.

## Example Usage

```terraform
data "materialize_source_reference" "source_references" {
source_id = materialize_source_mysql.test.id
}
output "source_references" {
value = data.materialize_source_reference.my_source_references.references
}
```

<!-- schema generated by tfplugindocs -->
## Schema

### Required

- `source_id` (String) The ID of the source to get references for

### Optional

- `region` (String) The region in which the resource is located.

### Read-Only

- `id` (String) The ID of this resource.
- `references` (List of Object) The source references (see [below for nested schema](#nestedatt--references))

<a id="nestedatt--references"></a>
### Nested Schema for `references`

Read-Only:

- `columns` (List of String)
- `name` (String)
- `namespace` (String)
- `source_database_name` (String)
- `source_name` (String)
- `source_schema_name` (String)
- `source_type` (String)
- `updated_at` (String)
65 changes: 65 additions & 0 deletions docs/data-sources/source_table.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
---
# generated by https://github.com/hashicorp/terraform-plugin-docs
page_title: "materialize_source_table Data Source - terraform-provider-materialize"
subcategory: ""
description: |-
---

# materialize_source_table (Data Source)



## Example Usage

```terraform
data "materialize_source_table" "all" {}
data "materialize_source_table" "materialize" {
database_name = "materialize"
}
data "materialize_source_table" "materialize_schema" {
database_name = "materialize"
schema_name = "schema"
}
```

<!-- schema generated by tfplugindocs -->
## Schema

### Optional

- `database_name` (String) Limit tables to a specific database
- `region` (String) The region in which the resource is located.
- `schema_name` (String) Limit tables to a specific schema within a specific database

### Read-Only

- `id` (String) The ID of this resource.
- `tables` (List of Object) The source tables in the account (see [below for nested schema](#nestedatt--tables))

<a id="nestedatt--tables"></a>
### Nested Schema for `tables`

Read-Only:

- `comment` (String)
- `database_name` (String)
- `id` (String)
- `name` (String)
- `owner_name` (String)
- `schema_name` (String)
- `source` (List of Object) (see [below for nested schema](#nestedobjatt--tables--source))
- `source_type` (String)
- `upstream_name` (String)
- `upstream_schema_name` (String)

<a id="nestedobjatt--tables--source"></a>
### Nested Schema for `tables.source`

Read-Only:

- `database_name` (String)
- `name` (String)
- `schema_name` (String)
13 changes: 13 additions & 0 deletions docs/data-sources/table.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,20 @@ description: |-



## Example Usage

```terraform
data "materialize_table" "all" {}
data "materialize_table" "materialize" {
database_name = "materialize"
}
data "materialize_table" "materialize_schema" {
database_name = "materialize"
schema_name = "schema"
}
```

<!-- schema generated by tfplugindocs -->
## Schema
Expand Down
Loading

0 comments on commit 9663cc4

Please sign in to comment.