Repository navigation
Diagnostics response includes service version and Sync Config source - #716
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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.
Based on Add service version and sync config source metadata to
/diagnosticsendpoint by @Manrich121, who can confirm the wording is accurate.Fixes #710
Released in PowerSync Service 1.27.1 (shipped by Version Packages #827, where the change appears under the 1.27.1 heading of the service-core changelog and in the service image changelog).
service(withservice.version, the version of the running Service) andsync_config_source(configwhen the Sync Config comes from the Service configuration, otherwiseapi). Verified against the diagnostics route and theDiagnosticsResponsetype in the source PR:serviceis always returned, andsync_config_sourceisconfigwhen a Sync Config is present in the Service configuration (inline, file path or base64), otherwiseapi.Left for the team: Add a non-fatal deprecation warning to Sync Rules (Phase 2), also in 1.27.1, adds a Sync Rules deprecation warning to the diagnostics
errors[]array. It is deprecation messaging, so I left it to you to decide whether and how the Errors and Warnings list should mention it.