Beer-garden

7/19/23

Other Changes

- Updated preview version of the new UI with better support for commands with
dynamic parameters
- Bumped dependency versions

2/1/23

Other Changes

- Preview version of the new UI now has intended feature parity with the
existing UI.

1/10/23

Other Changes

- Miscellaneous updates to the preview version of the new the UI

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)