-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create a physical rack table #156
Conversation
@@ -0,0 +1,5 @@ | |||
class AddPhysicalRackToPhysicalServers < ActiveRecord::Migration[5.0] | |||
def change | |||
add_column :physical_servers, :physical_rack_id, :bigint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't think you need/want to do this in its own migration, adding a column to the new table in the above migration is fine /cc @Fryguy opinions?
8723802
to
35adc18
Compare
@agrare resolved |
35adc18
to
2be9ef9
Compare
Checked commit felipedf@2be9ef9 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 |
@felipedf I just realized this didn't include an ems_ref column, which is generally required if the table is to be filled in during inventory refresh. |
This create a new table physical_racks and provides a :physical_rack_id column to physical_servers table.