Beer-garden

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)

1/4/22

Added Features

- File parameters on requests are now cleaned up by the pruner per the
`db.ttl.file` setting. (Issue 1215)
- File parameters are now cleaned up when the corresponding request is removed.
(Issue 1215)
- Reduce log noise generated from ERROR events. (Issue 1213)

Bug Fixes

- Request parameter and output data stored in GridFS no longer gets duplicated
throughout the life of a request. (Issue 1216)
- Request `status_updated_at` field on requests from child gardens is now
properly preserved. (Issue 1143)
- The DELETE method on the /api/v1/gardens endpoint has been restored. (Issue
1230)

Other Changes

- Added backend support for a command publishing blocklist that prevents
requests from listed commands from being published up to a parent garden. User
access to this feature will follow in a future release. (Issue 877)

12/8/21

Added Features

- The `status_updated_at` timestamp is now displayed on the Request view page.
(Issue 1142)
- The `/api/v1/job/<id>/execute` endpoint now takes an optional `reset_interval`
parameter which, when set to true, will update the next run time of an
interval trigger job to be based on the current adhoc execution, rather than
keeping the next run time that was based on the previously scheduled
execution. (Issue 1173)
- Command parameters of type `Bytes` are now rendered as a file upload dialog in
the tasking interface. Files provided this way will be properly sent down to
remote gardens for tasking, unlike the `Base64` paramter type. For this
reason, it is recommended that `Bytes` be used for parameters that intend to
take a file as input. (Issue 1165)

Bug Fixes

- Child requests are once again properly returned via the `/api/v1/request`
endpoint and properly displayed on the request page in the UI (Issue 1218)

Other Changes

- Added the following for use in future authorization related features:
- A trusted header login handler for authenticating users based on request
headers that indicate the username and a list of group memberships. (Issue
1198)
- Improved handling of refresh tokens in the UI (Issue 1187)
- Add authorization checks to the `/api/v1/forward` endpoint. (Issue 1207)

12/7/21

Bug Fixes

- Fixed an issue that prevented tasking of commands without parameters on remote
gardens (Issue 1209)