-
Notifications
You must be signed in to change notification settings - Fork 898
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
Remove DatabaseBackup #21415
Remove DatabaseBackup #21415
Conversation
0221da8
to
e59d4fb
Compare
e59d4fb
to
266f794
Compare
266f794
to
a5c86d4
Compare
a5c86d4
to
e61e544
Compare
@@ -31,12 +31,6 @@ | |||
:sched_action => {:method => "vm_scan"}, | |||
:miq_search_id => @search.id | |||
) | |||
|
|||
# DB Baskup Schedule |
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.
Baskup... 🤣
@jrafanie it was from when we were debugging the locking issues with the UI:
|
- name: evm_server_db_backup_low_space | ||
description: Server Database Backup Insufficient Space | ||
event_type: Default | ||
set_type: evm_operations |
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.
Will this require a data migration to ensure that any existing event defintions aren't tied to any existing objects, or will seed just take care of this?
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.
Oh... I don't know... I should probably look into that...
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.
I don't know how timelines or other graphs that show events over time would handle a reference to an event definition that no longer exists. Maybe it stored the definition information whatever it's displaying in the report result itself, similar to how we have a copy of the report definition in each result, in the situation where the report definition changed since it was included.
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.
Oh I wasn't even thinking of reports / timelines - I was more thinking things like policies where the event is the driver for the policy. So we'd have to remove the event from the policy, and then I guess if there are no events left we delete the entire policy.
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.
Is it better that we just keep this then? I just removed it because it had db_backup
in it, and I don't think anything else was going to be using it. But if we think it might have lingering uses, I don't mind just keeping it if it makes merging this simpler.
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.
If we intend to backport, then we can leave it for this PR, but if not, let's drop it... keeping it around, but having it never fire is worse because it sets up a user expectation that is wrong.
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.
I think I will remove this for now, but immediately open up a PR to fix this once it is merged so we can get most of this rolling, since I am unclear about what all is necessary, and I don't want this one thing holding things up.
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.
99001f1
to
5c4d6c6
Compare
not sure if we need a rebase or just to kick off the build again. I kicked one of them and will see if that fixes the first travis build |
5c4d6c6
to
1f68f0e
Compare
1f68f0e
to
0e59ada
Compare
Checked commits NickLaMuro/manageiq@5dc71b5~...0e59ada with ruby 2.6.3, rubocop 1.13.0, haml-lint 0.35.0, and yamllint |
Part of #21100
Depends on ManageIQ/manageiq-ui-classic#7816Depends on ManageIQ/manageiq-ui-classic#7943
Remove
DatabaseBackup
model and related code. Should be merged after related UI PR.Links
Possible UI PR: [WIP] Remove DatabaseBackup/FileDepot views manageiq-ui-classic#7816