adding backup filter by status#13254
Conversation
There was a problem hiding this comment.
could you try without updating this file
9fa3f09 to
b058f0a
Compare
|
@blueorangutan package |
|
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18055 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #13254 +/- ##
============================================
+ Coverage 18.09% 19.28% +1.18%
- Complexity 16732 16759 +27
============================================
Files 6037 5573 -464
Lines 542811 502641 -40170
Branches 66471 58896 -7575
============================================
- Hits 98230 96911 -1319
+ Misses 433533 394875 -38658
+ Partials 11048 10855 -193
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Description
Currently, the
listBackupsAPI does not allow listing backups based on their status. Changes have been made to the API to allow backups to be listed informing a specific status. In addition, the backups filter of the graphical interface has been extended to support the search based on status.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
The PR was tested by verifying both via CloudMonkey and the graphical interface the possibility of filtering backups by status.
How did you try to break this feature and the system with this change?
I tried to break this feature by passing an invalid status in both the CloudMonkey and the browser URL. In the API response a message was returned informing that the passed value is an invalid status.