release-1.11

This release features a couple of minor changes, kindly contributed by other developers:

• Allow sorting of nodes by Seen column in Orphaned view
  • #82
• improve db query performance
  • #84

No other changes compared to previous releases, other than an update to dependencies and a minor linting fixup detected by a newer release of staticcheck

release-1.10

This release updates the search-results page, to allow sorting any/all results which are returned.

Reported in #79, and resolved in #80.

This is probably the last release I'll make for the foreseeable future; I no longer have a working puppet-environment to develop and test-against. Without more contributions this will become an archived repository - and that's OK, it does the job, there are no significant failings.

release-1.9

This release overhauls how the handling of static-resources are implemented, and as a minor bug-fix includes the font-files which bootstrap expects to use.

Reported in #76, and resolved in #77.

release-1.8

This release contains a couple of smaller fixes to the environment-support which was introduced in the previous release as reported in #72. The artificial cap of 50 reports per-node was removed, as reported in #74.

Thanks to @corporate-gadfly for the bug-reports, and @plazonic for their work in updating the environment support.

release-1-7

This release contains support for Puppet Environments, via a drop-down at the top of the UI.

• Reported as a wishlist, a long time ago, in #54.
• Contributed by @plazonic as #71

release-1.6

This release is being made primarily to serve resources from within the binary, and to work behing a custom path:

• We also support being served from a custom prefix, as per #60
  • Contributed by @wetnun.
• Don't depend upon external resources #67
  • Fixed in #68.

There were some linter/CI changes but they were relatively minor.

This release is being made solely to transition the testing and release process from TravisCI to github actions:

• github-action-tester
  • Used to run tests.
• github-action-publish-binaries
  • Used to make releases.

This release contains a single bugfix, which was contributed by @attilasol, to resolve a problem reaping old entries.

• Pruning/auto-pruning not working due to locked database - #55.

This release is a bugfix-release which corrects the handling of sorting of the summary-views by date/time.

We'd previously been trying to sort dates, literally. Now we include the seconds-past-epoch as the sort-key for date/time fields, which means they sort correctly.

This release adds the ability to sort the columns in our various tables, as presented in the main tabs of the web-based user-interface.

This was, quickly, implemented via a user-suggestion in #53.

This release makes a couple of very minor changes:

• The HTTP-server sets up a default timeout of 300seconds / 5 minutes.
• The display of logs on the report-view shows where the log game from, in the manifest.
  • Thanks to @obi11235 for this contribution.

This release improves some of the internal details to handle error-conditions, and avoid them. There are no real user-visible changes, instead this release is about internal cleanup and tooling support.

It is now possible to submit metrics to a remote carbon server via the use of the golang-metrics library.

We've also moved from using go-bindata to my own tool for embedding resources into the binary, implant.

This release, unfortunately, drops binaries for different OS and architectures. This is necessary because the previous binaries just didn't work - each would complain about the lack of CGO being present for the SQLite3 library.

In terms of functional changes we now only regard nodes as orphaned if they've not been seen for three and a half days, rather than 24 hours. It is also possible to prune orphaned hosts, via "puppet-summary prune -orphaned"

This release updates the handling of the node view:

• Each report now has an ID listed, which corresponds to the point on the runtime-graph.
• Clicking upon a point in the graph-view will take you to the appropriate entry.

These changes are designed to allow a user to quickly identify a particularly slow/fast report, as documented in #45.

(Release 1.0.1 is a brief update to release-1.0 (withdrawn) which fixes a test-case failure I had not observed. Sorry for the churn!)

This release includes a couple of small fixups:

• The project contains a Dockerfile for simpler installation under docker.
• Reports which contain no changes can be pruned, via
  • puppet-summary prune -unchanged [-days 7]
  • Records of runs are still kept, but the report files are removed from disc and the UI doesn't contain links to the missing report.
• To ease running in a container a new flag -auto-prune has been added to the serve command.
  • Running "puppet-summary serve -auto-prune [flags]" will prune/reap reports older than 7 days, once per week, without the need to add a cronjob.

This release improves the display of the report-view, such that file-edits and similar are pre-formatted, which should make them easier to read.

This change was submitted by @matejzero - thanks :)

This release updates the handling of the end-point /api/state/${state}, allowing the caller to choose whether they prefer JSON, plain-text, or XML as output.

Allowing the caller to choose their preferred output-type matches our other end-points nicely, and has been documented in our API-guide.

This release continues to make improvements to the test-cases included in the source-repository, currently the coverage is hovering around 70%.

Beyond fixing some minor issues, and improving test-coverage, this new release introduces a new facility:

• Nodes are now searchable.

Every page of the UI now includes a search-box, allowing you to quickly & easily show nodes matching a given pattern.

This release improves the code quality, both in terms of the report card and the internal comments of the code-base.

The various views which are presented are now also fully scriptable, each view will return either:

• HTML
  • For viewing in your browser
• application/json
  • Which can be used for scripting-purposes
• application/xml
  • Which can be used for scripting-purposes

This support for returning different content-types, is fully documented in our API documentation. Our hacking guide has also been updated to demonstrate how you might cross-compile this code, useful if you wish to deploy upon a Raspberry Pi, for example.

This release introduces the display of "orphaned" nodes, nodes which have previously been heard from but which haven't submitted a report within a day.

It also introduces the "radiator-view", which is discoverable at the foot of ever page. Perfect for large status-screens.