ansible-community
UI: Add an auto-refresh to automatically refresh the page after a given duration
What is the idea ?
The built-in reporting UI doesn't have fancy asynchronous javascript that automatically pulls and update data without refreshing the page.
As a stopgap, it would be a nice alternative to allow for the page to refresh automatically every N seconds or N minutes.
It could look like this:
This could make the interface easier to use as a "live dashboard" that is always up to date.
Any updates on adding this feature? I'm constantly refresh to see the status of playbooks running. Even worst when running against multiple hosts
I agree that this would be nice to have :+1:
Looking at the mockup I did last year, I think I would do it differently today.
I think my idea at the time was to set a variable in the URL (say, autorefresh=60) for a value in seconds via those links in the dropdown menu.
It's probably way more convenient to set the refresh value in a cookie so it follows the user across pages easily without needing to include it in the URL everywhere. We don't set any cookies right now but there's ways to do it with django: https://docs.djangoproject.com/en/3.2/ref/request-response/#django.http.HttpResponse.set_cookie
Anyway, on refresh, we'd add a meta refresh with the value of the variable like this:
<meta http-equiv="refresh" content="{{ autorefresh }}">
Such that the browser refreshes the page automatically -- no need for javascript or anything else.
I don't have the code for the dropdown anymore and I can't find the branch for it but there's bootstrap docs about them here: https://getbootstrap.com/docs/4.6/components/dropdowns/
A drawback of that implementation is that it requires a new javascript dependency (popper.js) and it's harder to see whether auto-refresh would be enabled and what value it is set at.
I've tried thinking how we should implement it and I've come up with two mockups:
I thought the slider would be nice but it's harder to be precise in value without making the steps bigger like increments of 30s instead of 10s.
What do you think ? What should it look like ?
I'm busy with other stuff right now but it's something we could include in the upcoming release of 1.6.0 if someone wants to contribute it :p
I'm honestly a huge fan of the first mockup you did with the dropdown. I also agree either the refresh should be persisted via cookies. It would also be useful if we could set a default "Refresh Interval" via config/env variables.
I'm trying to wrap up 1.6.0 and thought we shouldn't forget about this (because I would like it too!) but it's not a blocker for the release -- we can do it for the next release.