Skip to content

Major regression in code host syncing / EXTSVC_CONFIG_FILE support?

Created by: slimsag

@sourcegraph/core-services Running ./enterprise/dev/start.sh on the latest master shows:

repo-updater | WARN Updating rate limiter, kind: AWSCODECOMMIT, err: internal rate limiting not support for AWSCODECOMMIT
repo-updater | WARN Syncer not started for unsupported code host, kind: GITLAB
repo-updater | WARN Syncer not started for unsupported code host, kind: AWSCODECOMMIT
repo-updater | WARN Syncer not started for unsupported code host, kind: GITLAB
repo-updater | INFO server listening, addr: 127.0.0.1:3182

This looks like a major regression in code host syncing support, since most customers use the EXTSVC_CONFIG_FILE to load configuration. What change introduced this?