Skip to content

campaigns: Changeset syncing will only happen in repo-updater

Warren Gifford requested to merge changeset-sync-rpc into master

Created by: ryanslade

We now only have one instance of campaigns.ChangesetSyncer which is instantiated during startup of enterprise/repo-updater.

Instead of creating a syncer from the frontend we now make an HTTP RPC call to repo-updater to enqueue the sync. The actual enqueing process has not been implemented yet and will be done in another PR, this change just refactors the code to make it possible.

The CreateChangesets mutation only returns ids now

This a breaking change since it changes the API. It is needed since syncing changesets happens asynchronously and we don't want the mutation to block. Also, the old approach would allow the possibility of returning a rate limit error to the user when trying to create changesets.

Merge request reports