Beer-garden

11/15/22

Added Features

- A preview of the new UI is now bundled into the official release RPM. This new
UI built on a more modern framework, but is largely intended to look and feel
similar to the existing UI. When using the configuration provided in the RPM,
the preview UI can be reached by appending /preview to the base beergarden URL
in your browser.

8/31/22

Added Features

- A new configuration option, `db.ttl.in_progress`, is now available for timing
out requests. Any request still in the `IN_PROGRESS` or `CREATED` status after
the configured timeout (set in minutes) will be marked as `CANCELLED`, making
it eligible for pruning.

Bug Fixes

- Viewing instance logs for systems on a local garden now works correctly.
- The Clear All Queues option on the system admin page now works correctly.
**NOTE:** This is supported for the local garden only.
- Fixed an issue where clearing the queue of an instance with non-word
characters in the instance name would raise an error. Queues can now be
cleared properly, regardless of the instance name.

Other Changes

- Reduced redundancy in the API calls made by the UI.
- Removed lingering internal references to beer garden v2 naming conventions.

6/28/22

Added Features

- The request output page now provides an option to render output that exceeds
the display size threshold. Note that the ability to successfully render such
output depends on both the output size and the client's available resources.
(Issue 1338)
- A Command Publishing Blocklist is now available. Commands on remote gardens
that are added to this list will not have their results published back up to
the parent. (Issue 1310)
- When launching a garden for the first time, the default user for running
plugins is now distinct from the default admin user. (Issue 1309)
- Improved display of multiline comments on requests. (Issue 242)
- Improved feedback when performing a garden sync. (Issue 1299)
- Roles are now synced to downstream gardens when performing a user sync. (Issue
1302)

Bug Fixes

- The namespaces and systems are now correctly displayed for the local garden in
both the API response and the garden admin view. (Issue 1300)
- Sensitive message queue connection information is no longer returned with the
systems API endpoint response. (Issue 1301)

Other Changes

- The superuser role is now internally managed and no longer needs to be
specifically listed in the role definition file. (Issue 1306)

4/12/22

**NOTE:** This release fixes an issue where client certificates would not be
sent to rabbitmq, even if beer garden was configured to do so. Connecting to
rabbitmq with certificates currently requires that the provided certificate be a
key and certificate bundle. Please be aware that in certain configurations where
the certificate is already set and is not a bundle, your connection to rabbitmq
may fail under this release. To fix this, switch your certificate to be a bundle
that also includes the key.

Bug Fixes

- Client certificates are now properly used when connecting to rabbitmq (Issue
1288).
- Column filtering headers on the Request page are now properly aligned (Issue
1286)
- Login form now provides feedback when entering invalid credentials (Issue
1280)

Other Changes

- The bgio/beer-garden:3-debian image and related images have been modified to
more closely align with the alpine image. Usage of the debian image should now
be the same as that of the alpine image.

3/21/22

Added Features

- A "Change Password" option has been added to the ☰ in the top right of the UI.
(Issue 1262)
- User management has been added to the UI for creating users and managing their
role assignments. This is available via a new "Users" option under the admin
menu. (Issue 1262)
- Requests now list the user that initiated the request. (Issue 1263)
- Users are now granted implicit access to any requests that they create. (Issue
1264)
- It is now possible to sync users and their role assignments between gardens.
(Issue 1265)
- A default admin user and superuser role will now be created during the first
startup of a new garden. (Issue 1274)

Bug Fixes

- Overly noisy "ERROR" event messages have been eliminated from the logs. These
had been especially prevalent in setups with remote gardens that were more
than a single hop away (i.e. "grandchildren"). (Issue 1271)

Other Changes

- A [security](https://beer-garden.io/docs/app/security/) section has been added
to the documentation on beer-garden.io, detailing how to use many of the User
management related features in this release.

2/9/22

Added Features

- Updates in status in the user interface (via WebSockets) are now filtered
according to a user's authorization, the same as HTTP API requests. (Issue
1243)
- The user interface now preemptively refreshes user access tokens so that a
user will not be automatically logged out after a short period of inactivity.
(Issue 1247)
- User interface elements are now hidden or displayed according to a user's
authorization to access their functionality. (Issue 1179 & Issue 1250)
- Users can now import and export Garden connection configurations via the user
interface. (Issue 1192 & Issue 1141)

Bug Fixes

- The Job error count now correctly also reflects those Jobs that fail due to an
exception, (Issue 1225)
- Job scheduler request handling now properly keeps track of which requests have
finished. (Issue 1214)

Other Changes

- Added basic documentation for authentication and authorization features added
to Beer-garden in previous releases. (Issue 1241)