Ask questionsDry-run external service configuration before saving
When saving an external service we call
repoupdater.DefaultClient.SyncExternalService with the configuration. However, we only do that once we have updated or created the external service in the DB. This is meant to trigger syncs of valid configurations. However, a user may put in incorrect values / unexpected queries resulting in errors or unexpected repos synced.
Adding an endpoint which does dry runs would allow the user to catch errors as well as understand how the configuration affects the set of repositories Sourcegraph syncs.
Answer questions slimsag
This seems like some relatively deep repo-updater changes and not in the scope of distribution, please correct me if I am wrong, though. Reassigning to cloud.