Geo: Project imports may not be synced if repository takes some time to fetch

In the logs, I think I see this behavior:

  1. User kicks off a project import
  2. The import job creates the project and launches a Sidekiq job to fetch the repository
  3. Geo secondary sees the creation of the project and goes to fetch.
  4. Geo secondary reports, "Repository is not found, marking it as successfully synced"
  5. Project import finishes

I think in Project#after_import, we might want to log a GeoRepositoryUpdatedEvent so the secondary does a resync.

Assignee Loading
Time tracking Loading