Beer-garden

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)

11/18/21

Added Features

- Requests now have a `status_updated_at` field representing the time of the
last status change. (Issue 1132)
- Added the ability to import and export jobs via the Scheduler page on the UI
(Issue 1034)
- Added the ability to do ad-hoc runs of scheduled jobs via both the API and UI
(Issues 1062, 1066)

Bug Fixes

- Properly validate input on the job import API (`/api/v1/import/job`) (Issue
1178)
- Dependency versions for development and deployment are now consistent (Issue
1182)

Other Changes

- Added the following for use in future authorization related features:
- Refresh token support (Issue 1171)
- The ability to enable permissions based authorization checks to the API
endpoints (Issues 1154, 1170)
- Various changes to the UI to support login / logout and refresh token
handling (Issue 1147)
- Added a concept of "global" permissions (Issue 1168)

10/15/21

Added Features

- Login endpoint added allowing user/password entry to receive a _JWT_ auth
token (Issue 1134)
- The `get_current_user` method in the `BaseHandler` class now gets the `User`
object based on the _JWT_ auth token (Issue 1144)
- Local and remote plugin logging config files now separated (Issue 817)
- Helper functions created to determine a user's permissions (Issue 1122)

Bug Fixes

- Hidden files in a plugin directory no longer show an error in the logs (Issue
1097)
- File parameters are now handled correctly and a file posted to a child garden
from the parent is correctly encoded and compressed for transport (Issue
1055)
- Dead runners on a child garden now correctly show their status on the parent's
UI (Issue 809)
- Stale systems are now removed when syncing child gardens (Issue 1101)
- Large requests now better determined whether they need to be stored in GridFS
(Issue 1038)

Other Changes

- Project is now able to accept pull requests from those who are working from a
fork
- Contribution guide updated

9/22/21

Added Features

- Added new api endpoints for importing and exporting jobs (Issue 1067)

Bug Fixes

- It is no longer possible to create multiple gardens sharing the same name
(Issue 727)
- GET and DELETE against the garden api endpoint now return the correct response
codes (Issue 1110)
- Fixed an issue where internal event processors were incorrectly modifying
events (Issue 978)
- Garden connection configuration is now properly displayed in the UI when
default values are being used (Issue 1104)
- Connection reliability fixes for the stomp entrypoint (Issue 1102)

Other Changes

- Added the following for use in future authorization related features:
- Authorization related database models (Issue 1089)
- The ability to load role definitions from a configuration file (Issue 1091)
- Updated library dependency versions