1. 25 Apr, 2018 3 commits
    • Zeger-Jan van de Weg's avatar
      Drop NULL constraint on Geo event columns · 72014170
      Zeger-Jan van de Weg authored
      The columns effected store the repository storage path, which can't be
      NULL. So in general the path can't be NULL. However, the tables also
      include the shard name. From the shard name, the storage path can be
      determined, allowing for a more dynamic approach.
      72014170
    • Zeger-Jan van de Weg's avatar
      Revert migration dropping columns in one release · e2529196
      Zeger-Jan van de Weg authored
      During the review of gitlab-org/gitlab-ee!5389 it was noticed that the
      docs mandated ignoring a column first, and a release later dropping it.
      
      Given this migration is nearly finished, I've reverted the changes in
      one commit so this commit can be reverted itself and picked on a new
      branch.
      e2529196
    • Zeger-Jan van de Weg's avatar
      GitLab Shell doesn't require a path, now a shard name · 6782a18d
      Zeger-Jan van de Weg authored
      Picked from CE, from: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18364
      
      But includes the EE changes too. Among the required changes are dropping
      of repository_storage_path from Geo tables.
      
      Geo stored `repository_storage_path` in four models, which initially was
      modeled after the interface of Gitlab::Shell rather than storing only
      the needed data. Given this inferred data had no place nor need to be
      stored I opted for deleting it.
      6782a18d
  2. 24 Apr, 2018 6 commits
  3. 23 Apr, 2018 31 commits