Skip to content

Releases: voxpupuli/puppetboard

v5.4.0

01 Mar 11:36
v5.4.0
0789c88
Compare
Choose a tag to compare

Full Changelog

Merged pull requests:

v5.3.0

07 Feb 19:08
v5.3.0
05b286b
Compare
Choose a tag to compare

Full Changelog

Implemented enhancements:

Merged pull requests:

v5.2.0

17 Jan 22:26
v5.2.0
7414c1f
Compare
Choose a tag to compare

Full Changelog

Implemented enhancements:

  • Update README for SECRET_KEY and SSL Setup #985 (tuxmea)

Fixed bugs:

  • Facts only showing RedHat #961

Closed issues:

  • Make it More Apparent that SECRET_KEY cannot be blank #978

Merged pull requests:

v5.1.0

08 Oct 20:22
v5.1.0
c8b0d45
Compare
Choose a tag to compare

Merged pull requests:

v5.0.0

27 Jul 11:45
895030f
Compare
Choose a tag to compare
  • Stop setting SECRET_KEY value to a random string by default. This has caused issues in deployments with more than one app replica or when the app was restarted. Please set this to your own long, random string, the same for each application replica. Implements #721.
  • Drop support for Python 3.7 (end-of-life in June 2023). PR #899
  • Fix broken links in Classes view. PR #868, fixes #816.
  • Fix if fact is None (default for full node view). PR #908, fixes #907.
  • Dependencies update.

Thanks to the following contributors of this release:

v4.3.0

04 Apr 17:27
Compare
Choose a tag to compare
  • Add new Classes view. This view lists the Puppet classes that have had at least one of their resources changed (event). (#799).

Big thanks to Louis Charreau who contributed the above feature!

v4.2.6

10 Feb 09:42
Compare
Choose a tag to compare
  • Fix auto-resize in the Radiator view in offline mode (#718).

Thanks to René Hernandez 2nd who contributed to this release!

v4.2.5

09 Jan 11:00
Compare
Choose a tag to compare
  • Really fix starting the app when the SECRET_KEY is set to bytes instead of str. (#741).

v4.2.4

05 Jan 16:31
Compare
Choose a tag to compare
  • Fix starting the app when the SECRET_KEY is set to bytes instead of str. (#741).

v4.2.3

10 Dec 12:36
Compare
Choose a tag to compare
  • Sort 'uptime' fact values correctly again - it was fixed in v3.4.0 but got broken in v4.1.0 (#469).