You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Feature] Customize and document event_log block in databricks_pipeline (#4612)
## Changes
<!-- Summary of your changes that are easy to understand -->
The only required parameter is `event_log.name`, the `catalog` and
`schema` are inherited from the pipeline settings.
## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->
- [x] `make test` run locally
- [x] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] using Go SDK
- [ ] using TF Plugin Framework
Copy file name to clipboardExpand all lines: docs/resources/pipeline.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,10 @@ The following arguments are supported:
97
97
*`gateway_storage_catalog` - Required, Immutable. The name of the catalog for the gateway pipeline's storage location.
98
98
*`gateway_storage_name` - Required. The Unity Catalog-compatible naming for the gateway storage location. This is the destination to use for the data that is extracted by the gateway. Delta Live Tables system will automatically create the storage location under the catalog and schema.
99
99
*`gateway_storage_schema` - Required, Immutable. The name of the schema for the gateway pipelines's storage location.
100
-
100
+
*`event_log` - an optional block specifying a table where DLT Event Log will be stored. Consists of the following fields:
101
+
*`name` - (Required) The table name the event log is published to in UC.
102
+
*`catalog` - (Optional, default to `catalog` defined on pipeline level) The UC catalog the event log is published under.
103
+
*`schema` - (Optional, default to `schema` defined on pipeline level) The UC schema the event log is published under.
0 commit comments