gitlab-org--gitlab-foss/db/migrate/20170629171610_rename_appli...

class RenameApplicationSettingsSigninEnabledToPasswordAuthenticationEnabled < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  DOWNTIME = false

  disable_ddl_transaction!

  def up
    rename_column_concurrently :application_settings, :signin_enabled, :password_authentication_enabled
  end

  def down
    cleanup_concurrent_column_rename :application_settings, :password_authentication_enabled, :signin_enabled
  end
end
Add version 4.2 to all existing migrations DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912 2018-11-13 07:27:31 +00:00			`class RenameApplicationSettingsSigninEnabledToPasswordAuthenticationEnabled < ActiveRecord::Migration[4.2]`
Fixes needed when GitLab sign-in is not enabled When sign-in is disabled: - skip password expiration checks - prevent password reset requests - don’t show Password tab in User Settings - don’t allow login with username/password for Git over HTTP requests - render 404 on requests to Profiles::PasswordsController 2017-06-27 18:02:09 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`disable_ddl_transaction!`

			`def up`
			`rename_column_concurrently :application_settings, :signin_enabled, :password_authentication_enabled`
			`end`

			`def down`
			`cleanup_concurrent_column_rename :application_settings, :password_authentication_enabled, :signin_enabled`
			`end`
			`end`