Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pipeline docs for default development flag value #1669

Merged
merged 1 commit into from
Oct 14, 2022

Conversation

bradfordchang
Copy link
Contributor

Per DLT Settings Docs, the development flag defaults to true.

Updating the docs for the provider to have the correct default.

Per [DLT Settings Docs](https://docs.databricks.com/workflows/delta-live-tables/delta-live-tables-configuration.html#settings), the `development` flag defaults to `true`.

Updating the docs for the provider to have the correct default.
@codecov-commenter
Copy link

Codecov Report

Merging #1669 (4b2d7b5) into master (46da779) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1669   +/-   ##
=======================================
  Coverage   89.97%   89.97%           
=======================================
  Files         141      141           
  Lines       11063    11063           
=======================================
  Hits         9954     9954           
  Misses        707      707           
  Partials      402      402           

@nfx nfx merged commit 9559901 into databricks:master Oct 14, 2022
@nfx nfx mentioned this pull request Oct 17, 2022
michael-berk pushed a commit to michael-berk/terraform-provider-databricks that referenced this pull request Feb 15, 2023
)

Per [DLT Settings Docs](https://docs.databricks.com/workflows/delta-live-tables/delta-live-tables-configuration.html#settings), the `development` flag defaults to `true`.

Updating the docs for the provider to have the correct default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants