This bar reduces the available vertical space and other maintainers feel
it better to remove it than to modify it.
Also reducing the specific mention of @daenney from README.rst since he
has steped down as main project maintainer.
"Skips" were highlighted with orange on one page and yellow on another. This change makes them consistent, and switches the color to "black" for accessibility reasons. (The contrast between the shades of orange and red used for skips and errors was *very* low. Indistinguishable on some screens.)
A new endpoint in the header, Catalogs, takes the user to a page with a node
table similar to that in the nodes page. This table shows the node with a
link to the node page, the catalog timestamp with a link to the catalog
page and a small form with a select field to be used to compare the
catalog of this row's node with that of another node.
This makes use of the available catalog endpoints in pypuppetdb and PuppetDB
and displays to administrators the last compiled catalog for a node,
if the variable ENABLE_CATALOG is True (defaults to False)
Added inventory page showing a table similar to the "Nodes" one,
but containing any customizable set of facts.
A setting INVENTORY_FACTS has been added. It controls the list
of facts to be displayed along with a description for the header
of the table.
When there are more than 15 unique fact values it groups the least
commonly used into an other label.
Co-authored-by: Sage Imel <sage@cat.pdx.edu>
Co-authored-by: Ryan Niebur <ryan@cat.pdx.edu>
chart.js is poorly maintained and has been disabled. c3.js
has active development and removes the need for two charts
on the facts page.
Co-authored-by: Sage Imel <sage@cat.pdx.edu>
Co-authored-by: Ryan Niebur <ryan@cat.pdx.edu>
To align with added offline resources:
* Semantic UI from 0.12.0 to 0.16.1
(0.18.0 is not yet available on cdnjs.cloudflare.com)
* jQuery TableSorter from 2.13.3 to 2.17.2
* moment.js from 2.5.1 to 2.7.0
We actually had a function that would sort the facts tables by default
based on the first column but weren't using this. Testing with the
upcoming PuppetDB 1.6 made this bug surface because PuppetDB stopped
sorting facts by itself.
* report/latest/<node_name> uses limit parameter in _query
to get just one report
* disable "Latest Report" button if there is no report
* HTTP Status 500 if there is no report on report/latest/<node_name>
