[Feature] Handle schema attribute in databricks_pipeline
#4137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The new `schema` attribute was added to support direct publishing mode. Besides documentation we were need to add TF schema customization as it conflicts with the `target` attribute.
rauchy
approved these changes
Oct 23, 2024
rauchy
added a commit
that referenced
this pull request
Oct 23, 2024
### New Features and Improvements * Add `databricks_alert` resource to replace `databricks_sql_alert` ([#4051](#4051)). * Added resource `databricks_custom_app_integration` ([#4124](#4124)). * Handle `schema` attribute in `databricks_pipeline` ([#4137](#4137)). ### Bug Fixes * Change repo used in test ([#4122](#4122)). ### Documentation * Clarify that `graviton` option of `databricks_node_type` could be used on Azure ([#4125](#4125)). * Fix argument in example for `databricks_custom_app_integration` ([#4132](#4132)). * Fix for UC on AWS guide - use `databricks_aws_unity_catalog_assume_role_policy` where necessary ([#4109](#4109)). ### Exporter * **Breaking change**: Move `databricks_workspace_file` to a separate service ([#4118](#4118)). * Exclude some system schemas from export ([#4121](#4121)). * Use `List` + iteration instead of call to `ListAll` ([#4123](#4123)).
rauchy
added a commit
that referenced
this pull request
Oct 24, 2024
### New Features and Improvements * Add `databricks_alert` resource to replace `databricks_sql_alert` ([#4051](#4051)). * Add `databricks_query` resource instead of `databricks_sql_query` ([#4103](#4103)). * Added resource `databricks_custom_app_integration` ([#4124](#4124)). * Handle `schema` attribute in `databricks_pipeline` ([#4137](#4137)). ### Bug Fixes * Change repo used in test ([#4122](#4122)). ### Documentation * Clarify that `graviton` option of `databricks_node_type` could be used on Azure ([#4125](#4125)). * Fix argument in example for `databricks_custom_app_integration` ([#4132](#4132)). * Fix for UC on AWS guide - use `databricks_aws_unity_catalog_assume_role_policy` where necessary ([#4109](#4109)). ### Exporter * **Breaking change**: Move `databricks_workspace_file` to a separate service ([#4118](#4118)). * Exclude some system schemas from export ([#4121](#4121)). * Use `List` + iteration instead of call to `ListAll` ([#4123](#4123)).
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 24, 2024
### New Features and Improvements * Add `databricks_alert` resource to replace `databricks_sql_alert` ([#4051](#4051)). * Add `databricks_query` resource instead of `databricks_sql_query` ([#4103](#4103)). * Added resource `databricks_custom_app_integration` ([#4124](#4124)). * Handle `schema` attribute in `databricks_pipeline` ([#4137](#4137)). ### Bug Fixes * Change repo used in test ([#4122](#4122)). ### Documentation * Clarify that `graviton` option of `databricks_node_type` could be used on Azure ([#4125](#4125)). * Fix argument in example for `databricks_custom_app_integration` ([#4132](#4132)). * Fix for UC on AWS guide - use `databricks_aws_unity_catalog_assume_role_policy` where necessary ([#4109](#4109)). ### Exporter * **Breaking change**: Move `databricks_workspace_file` to a separate service ([#4118](#4118)). * Exclude some system schemas from export ([#4121](#4121)). * Use `List` + iteration instead of call to `ListAll` ([#4123](#4123)). Co-authored-by: Omer Lachish <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
The new
schemaattribute was added to support direct publishing mode. Besides documentation we were need to add TF schema customization as it conflicts with thetargetattribute.Tests
make testrun locallydocs/folderinternal/acceptance