-
Notifications
You must be signed in to change notification settings - Fork 127
Add --strict to bundle validate #4232
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
base: main
Are you sure you want to change the base?
Conversation
| Run validate before deploy to catch configuration issues early: | ||
| databricks bundle validate # Validate default target | ||
| databricks bundle validate --target prod # Validate specific target | ||
| databricks bundle validate --target prod # Validate specific target |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whitespace change?
| foo: | ||
| default: true | ||
|
|
||
| bar: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the purpose of 2 targets here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to test that both for 1 warning and multiple warnings, the error message is correct.
|
Commit: ddaacb7
27 interesting tests: 17 KNOWN, 7 RECOVERED, 2 flaky, 1 SKIP
Top 44 slowest tests (at least 2 minutes):
|
Some of our warnings cause errors down the line. For example, if required values are missing or invalid enum values are provided.
The
--strictflag allows users to opt-in into a more strict validation that can help them enforce our recommendations better.