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
Retirement - use datetime instead of date - migration #11156
Retirement - use datetime instead of date - migration #11156
Conversation
… no date columns in the db
…(or Time.now.to_date) + removed retires_on_date()
…ement set on #{retires_on}" +- details makes retires_on_date function useless
.in_time_zone can convert Date, Time, DateTime and String
Checked commits https://github.com/himdel/manageiq/compare/298963247759838bd9eeba5cd6ad25cd0620c7eb~...f728ef10876fa68bdb7c01be96f0d69b700580e1 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1 app/models/mixins/retirement_mixin.rb
spec/lib/miq_expression_spec.rb
|
@gmcculloug can you review please? I'd like to get this in before the migration freeze.. @dclarizio cc, should be ready (I hope..) |
The retires_on field was changed from a `:date` column to a `:datetime` which now requires the days(in seconds) be added to the time. - Depends on: ManageIQ/manageiq#14143 - This issue was introduced in PR ManageIQ/manageiq#11156 - https://bugzilla.redhat.com/show_bug.cgi?id=1427503 Signed-off-by: Sachin <psachin@redhat.com>
This was originally a part of #7471, splitting off the backend part for easier review/merge..
This changes the
retires_on
field from:date
to:datetime
- the idea is that we will change the UI to let the user pick a specific point in time (including timezone) for the machine to retire, instead of a rather vague "that day +- 23.5 hours" (yay timezones!).(
retirement_last_warn
already IS a datetime)https://bugzilla.redhat.com/show_bug.cgi?id=1316632
UI changes are limited to adding time and time zone info to the messages and summaries...