Uh oh!
There was an error while loading. Please reload this page.
libs/dyn/convert: suppress "unknown field" warnings for anchor containers - #5975
Merged
Conversation
…ners
Bundle validation already suppresses "unknown field" warnings for
standalone YAML anchors, but still warns when anchors are grouped inside
a list or map, the common pattern of collecting reusable blocks under an
x-* key:
x-anchors:
- &a { name: foo }
- &b { name: bar }
This adds a recursive isAnchorContainer check so a non-empty sequence or
map whose elements are all anchors (or all anchor containers) is treated
the same as a standalone anchor and does not trigger the warning. Empty
containers and containers with any non-anchor element still warn as
before. The unknown field is dropped from the normalized output
regardless; only the spurious warning is suppressed.
Co-authored-by: IsaacCo-authored-by: Isaac
The suppression does not depend on the x-* prefix, so use plain keys. Co-authored-by: Isaac
Co-authored-by: Isaac
Co-authored-by: Isaac
eng-dev-ecosystem-bot
commented
Jul 20, 2026
Collaborator
Integration test reportCommit: 286272a
8 interesting tests: 4 RECOVERED, 4 SKIP
Top 10 slowest tests (at least 2 minutes):
|
Uh oh!
There was an error while loading. Please reload this page.
andrewnester
approved these changes
Jul 20, 2026
The acceptance test only exercised the no-warning path. Extend it to also cover a container nested inside a container and a mixed container that holds a non-anchor element (which is reported as an unknown field), documenting the rationale for not suppressing the mixed case. Co-authored-by: Isaac
Remove the parenthetical about x-* keys from the isAnchorContainer doc comment and rename the unit test's unknown field from x-thing to thing, so neither uses the x- prefix. Co-authored-by: Isaac
pietern
enabled auto-merge
July 21, 2026 14:20
janniklasrose
approved these changes
Jul 21, 2026
eng-dev-ecosystem-bot
commented
Jul 21, 2026
Collaborator
Integration test reportCommit: 1365452
8 interesting tests: 4 SKIP, 3 KNOWN, 1 RECOVERED
Top 3 slowest tests (at least 2 minutes):
|
eng-dev-ecosystem-bot
commented
Jul 21, 2026
Collaborator
Integration test reportCommit: 195c987
33 interesting tests: 21 FAIL, 6 KNOWN, 4 flaky, 2 SKIP
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Jul 22, 2026
## Release v1.9.0 ### CLI * `databricks auth profiles` no longer stalls on an unreachable workspace and instead fails validation after 5 seconds per host ([#5928](#5928)). * Fixed `databricks fs rm -r` failing on UC Volumes backed by GCS when a directory becomes empty during recursive deletion ([#5958](#5958)). * You can now ask questions about your data directly from the CLI with `databricks genie ask "..."`. Genie answers natural-language questions ("what were total sales last month?", "which tables are in the sales catalog?"), runs the query inside Databricks, and renders the answer in the terminal. This promotes the former `databricks experimental genie ask` command; the experimental alias still works but is deprecated and will be removed in a future release ([#6010](#6010)). ### Bundles * `bundle validate` now reports a clear error when a `sql_warehouse` is missing a `name` (including whitespace-only names), and a warning when a grant is missing a `principal` ([#5818](#5818)). * Bundle templates now scaffold an `AGENTS.md` that points coding agents at Databricks AI Tools, alongside a minimal `CLAUDE.md` that includes it via `@AGENTS.md` ([#5996](#5996)). * `bundle generate job` can now download workspace files referenced by `spark_python_task`, rewriting them to a relative path like it already does for notebooks. This is opt-in via the `--download-spark-python-files` flag ([#5799](#5799)). * Simplified the `default-minimal` bundle template and added an alias `databricks bundle init empty` ([#5899](#5899)). * Add support for the `instance_pools` resource type in Declarative Automation Bundles. Instance pools are only supported in direct deployment mode. * Do not emit "unknown field" warnings for YAML anchors grouped in a list or map, matching the existing suppression for standalone anchors ([#5975](#5975)). * Provide an actionable error message if databricks.yml is missing or DATABRICKS_BUNDLE_ROOT is invalid ([#5953](#5953)). ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.154.0 to v0.160.0 ([#5982](#5982)). * Bump Terraform provider from v1.121.0 to v1.122.0 ([#5977](#5977)).
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Bundle validation already suppresses "unknown field" warnings for standalone YAML anchors, but still warns when anchors are grouped inside a list or map, the common pattern of collecting reusable blocks under an
x-*key:This adds a recursive
isAnchorContainercheck so a non-empty sequence or map whose elements are all anchors (or all anchor containers) is treated the same as a standalone anchor and does not trigger the warning. Empty containers and containers with any non-anchor element still warn as before. The unknown field is dropped from the normalized output regardless; only the spurious warning is suppressed.This pull request and its description were written by Isaac.