Repository navigation
config-remote-sync: fail when a selected resource is not in the configuration - #6931
Merged
Merged
Conversation
…guration Co-authored-by: Isaac <no-reply@databricks.com>
…ied error codes Co-authored-by: Isaac <no-reply@databricks.com>
Collaborator
Integration test reportCommit: 3609192
Top 6 slowest tests (at least 2 minutes):
|
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
denik
approved these changes
Oct 6, 2026
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
bundle config-remote-sync --select-idsnow fails when a selected resource is deployed but its key is no longer in the bundle configuration (renamed or removed since the last deploy). JSON output reportsstatus: failedwith a newerrorCodefield (RESOURCE_NOT_IN_CONFIG), and telemetry records the same category.errorCodeis only set for explicitly classified failures.Why
Such a resource is planned as a delete with no changes, so the command reported success and the remote edits were silently dropped. DABs in the Workspace showed the sync as successful.
Tests
Added an acceptance test that renames a deployed job's key and checks the JSON output and the telemetry payload.