Repository navigation
test: list the new features resource as a known schema gap - #232
Merged
Merged
Conversation
This file contains hidden or 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
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.
Databricks CLI v1.22.0 added a
featuresbundle resource (databricks/cli#6952). The schema coverage check on the latest CLI now fails because the inspector neither models it nor lists it as a known gap.This adds
featurestoKNOWN_RESOURCE_GAPS. These resources still render as generic nodes. Proper support can follow later.Verified:
npm run test:schema-coveragepasses against CLI v1.21.0 and v1.22.1.