1. 29 Jun, 2017 5 commits
    • Michael Kozono's avatar
      Add default to authorized_keys_enabled setting · 00236339
      Michael Kozono authored
      Reminder: The original migration was fixed retroactively a few commits ago, so people who did not ever run GitLab 9.3.0 already have a column that defaults to true and disallows nulls. I have tested on PostgreSQL and MySQL that it is safe to run this migration regardless.
      
      Affected customers who did run 9.3.0 are the ones who need this migration to fix the authorized_keys_enabled column.
      
      The reason for the retroactive fix plus this migration is that it allows us to run a migration in between to fix the authorized_keys file only for those who ran 9.3.0.
      00236339
    • Michael Kozono's avatar
      Ensure `authorized_keys_enabled` defaults to true · f6ace56e
      Michael Kozono authored
      Locally, if Spring was not restarted, `current_application_settings` was still cached, which prevented the migration from editing the file. This will also ensure that any app server somehow hitting old cache data will properly default this setting regardless.
      f6ace56e
    • Michael Kozono's avatar
      Fix authorized_keys file if needed · febc26e4
      Michael Kozono authored
      febc26e4
    • Michael Kozono's avatar
      Retroactively fix migration · a97f5f73
      Michael Kozono authored
      This allows us to identify customers who ran the broken migration. Their `authorized_keys_enabled` column does not have a default at this point.
      
      We will fix the column after we fix the `authorized_keys` file.
      a97f5f73
    • Michael Kozono's avatar
      Revert "Merge branch 'dm-revert-authorized-files-toggle-master' into 'master'" · 526a05e7
      Michael Kozono authored
      This reverts commit fce9c01b, reversing
      changes made to b1003408.
      
      To reiterate: this reverts a revert.
      526a05e7
  2. 28 Jun, 2017 18 commits
  3. 27 Jun, 2017 17 commits