Bonny v1.0.0 Release Notes
Release Date: 2022-11-28 // 6 months ago-
๐จ With Version 1.0.0, Bonny got a thorough refactoring. Besides this changelog, you might consider the several guides (e.g. the [migration guide](./guides/migration.mid))
Bonny.Operator
was introduced as an entry point to the watching and handling of processes. Your controllers are not more added to the supervision tree by bonny. Instead you must create an operator and add that to your application's supervision tree.- ๐ฆ The
Pluggable
(thinkPlug
) library is used withBonny.Axn
as token to processADDED
,MODIFIED
,DELETED
and reconciliation events byPluggable
pipelines. Bonny.ControllerV2
was introduced as a successor toBonny.Controller
. It leveragesPluggable.StepBuilder
(thinkPlug.Builder
) to build a pluggable pipeline.Bonny.Event
andBonny.EventRecorder
were introducd for Kubernetes event creation (#156, #5)
๐จ Why this refactoring?
- ๐ Allows for better CRD and API version definitions
- โ
With a
Pluggable
architecture, controllers are much easier to test (Think ofPlug.Conn
tests) - The
Pluggable
architecture makes your processing pipelines composable and simpler to customize/extend - Decoupling of manifest generation and action event processing
- Internally, the amount of macros was reduced which makes Bonny easier to understand and maintain
Previous changes from v1.0.0-rc.3
-
๐ Fixed
- ๐
Bonny.Mix.Operator
- fix manifest generation: remove version from apiGroup in ClusterRole.
- ๐