Refresh host tab in job invocation detail together with overall status
when reviewing a job status, I could see multiple requests in the same second for refresh.
this is caused due to how the refresh is triggered (every time you get a response from the server, you immediately start to ask for another refresh).
IMHO this logic should be extracted from the rails response code, and managed once within the initial js that is loaded.
related, the host tab is not updated, and requires a manual update.
Refs #12065 - fix foreman 1.9 compatibility with refresh js
Foreman 1.9 didn't include underscore.js, but we are ok with jQuery in
#3 Updated by Marek Hulán over 7 years ago
- Subject changed from job review refresh interval is too high to Refresh host tab in job invocation detail together with overall status
- Status changed from New to Assigned
- Assignee set to Marek Hulán
- Target version set to 87
I think it will be more efficient to do the update together in same request for which we do the chart update. We won't refresh the whole table, just hosts that hasn't finish the run yet. Otherwise we'd have to deal with pagination, also is user would select some text it would remove the selection etc...