gitlab-org--gitlab-foss/db/migrate/20150812080800_add_settings_import_sources.rb

# rubocop:disable all
require 'yaml'

class AddSettingsImportSources < ActiveRecord::Migration[4.2]
  def change
    unless column_exists?(:application_settings, :import_sources)
      add_column :application_settings, :import_sources, :text
      import_sources = YAML::dump(Settings.gitlab['import_sources'])
      execute("update application_settings set import_sources = '#{import_sources}'")
    end
  end
end
Enable RuboCop for migrations Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file. 2016-06-09 08:39:16 -04:00			`# rubocop:disable all`
Import sources: settings in the admin interface 2015-08-12 02:13:20 -04:00			`require 'yaml'`

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 02:27:31 -05:00			`class AddSettingsImportSources < ActiveRecord::Migration[4.2]`
Import sources: settings in the admin interface 2015-08-12 02:13:20 -04:00			`def change`
			`unless column_exists?(:application_settings, :import_sources)`
			`add_column :application_settings, :import_sources, :text`
			`import_sources = YAML::dump(Settings.gitlab['import_sources'])`
			`execute("update application_settings set import_sources = '#{import_sources}'")`
			`end`
			`end`
			`end`