config-remote-sync: skip changes nested inside a variable reference - #6308
Open
ilyakuz-db wants to merge 2 commits into
Open
config-remote-sync: skip changes nested inside a variable reference#6308ilyakuz-db wants to merge 2 commits into
ilyakuz-db wants to merge 2 commits into
Conversation
Co-authored-by: Isaac
Contributor
Approval status: pending
|
Collaborator
Integration test reportCommit: 597126c
9 interesting tests: 4 SKIP, 3 KNOWN, 1 RECOVERED, 1 flaky
Top 7 slowest tests (at least 2 minutes):
|
Co-authored-by: Isaac
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.
Changes
config-remote-syncnow skips a change whose parent field in the YAML is a variable reference (e.g.spark_conf: ${var.spark_conf}) instead of failing the whole run. Such skips are recorded in the existing skipped-changes telemetry.Why
A nested key or index cannot be written into a scalar
${var}node, so the write-back aborted the entire sync and dropped every other detected change. Skipping only the unwritable change lets the rest apply.Tests
Added an acceptance test: a remotely-added key under a
${var}field is skipped while an unrelated edit still syncs.