tag these migrations as predeploy

They add a column and a table, so they need to happen before the new code that uses that new schema is running Change-Id: I9b9eb1c175af91eba7042906ae5fbf66fd9516e2 Reviewed-on: https://gerrit.instructure.com/12764 Reviewed-by: Cody Cutrer <cody@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2012-08-06 16:00:06 -06:00 · 2012-08-06 16:00:06 -06:00 · 06588fc825
parent 6c10743864
commit 06588fc825
2 changed files with 2 additions and 2 deletions
--- a/db/migrate/20120716204625_add_visibility_to_user_services.rb
+++ b/db/migrate/20120716204625_add_visibility_to_user_services.rb
@ -1,5 +1,5 @@
 class AddVisibilityToUserServices < ActiveRecord::Migration
-  tag :postdeploy
+  tag :predeploy

  def self.up
    add_column :user_services, :visible, :boolean
--- a/db/migrate/20120718161934_create_user_profile_links_table.rb
+++ b/db/migrate/20120718161934_create_user_profile_links_table.rb
@ -1,5 +1,5 @@
 class CreateUserProfileLinksTable < ActiveRecord::Migration
-  tag :postdeploy
+  tag :predeploy

  def self.up
    create_table :user_profile_links do |t|