gitlab-org--gitlab-foss/db/migrate/20180907015926_add_legacy_a...

# frozen_string_literal: true

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

  DOWNTIME = false

  disable_ddl_transaction!

  def up
    add_column_with_default(:cluster_providers_gcp, :legacy_abac, :boolean, default: true)
  end

  def down
    remove_column(:cluster_providers_gcp, :legacy_abac)
  end
end
Create a GKE cluster with legacy_abac disabled when the `:rbac_clusters` feature flag is enabled Explicitly persist the legacy_abac value of the cluster_provider_gcp so that we can disable abac if the `:rbac_clusters` feature flag is enabled 2018-09-07 03:07:47 +00:00			`# frozen_string_literal: true`

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 AddLegacyAbacToClusterProvidersGcp < ActiveRecord::Migration[4.2]`
Create a GKE cluster with legacy_abac disabled when the `:rbac_clusters` feature flag is enabled Explicitly persist the legacy_abac value of the cluster_provider_gcp so that we can disable abac if the `:rbac_clusters` feature flag is enabled 2018-09-07 03:07:47 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`disable_ddl_transaction!`

			`def up`
			`add_column_with_default(:cluster_providers_gcp, :legacy_abac, :boolean, default: true)`
			`end`

			`def down`
			`remove_column(:cluster_providers_gcp, :legacy_abac)`
			`end`
			`end`