KubeOps.Testing 3.0.0-prerelease.2

• net5.0

  • KubeOps (>= 3.0.0-prerelease.2)
  • Microsoft.AspNetCore.Mvc.Testing (>= 5.0.2)

# [3.0.0-prerelease.2](https://github.com/buehler/dotnet-operator-sdk/compare/v3.0.0-prerelease.1...v3.0.0-prerelease.2) (2021-01-29)


### Code Refactoring

* **controller:** Refactoring to scoped controllers. ([17d636f](https://github.com/buehler/dotnet-operator-sdk/commit/17d636f7310a7cb0885b28534c05bead22b80bcc)), closes [#138](https://github.com/buehler/dotnet-operator-sdk/issues/138)
* **finalizer:** Use scoped finalizer. ([307cc55](https://github.com/buehler/dotnet-operator-sdk/commit/307cc556baabb525b717fb1a9d516862c195b491))
* **function naming:** Use best practice names. ([4e675b8](https://github.com/buehler/dotnet-operator-sdk/commit/4e675b8546e08eb887fcc655d944fc12a4d8df0e))
* **testing:** Adjust test helpers according to breaking changes. ([163c18b](https://github.com/buehler/dotnet-operator-sdk/commit/163c18b92b5b074f7f2693ecc3946166d7e45f01))
* **validators:** Use scoped validators and register by type. ([a63b511](https://github.com/buehler/dotnet-operator-sdk/commit/a63b5116f39079f7c19eaee9fbc021430fae3a6f))


### BREAKING CHANGES

* **testing:** This removes the mocked event queue.
To test controllers and finalizers, use the provided
methods of the KubernetesOperatorFactory to enqueue
events and finalizers.
* **validators:** Validators do not need to be registered via
`AddValidationWebhook` method. All validators are infered/searched
by type when they implement the `IValidationWebhook<>` interface.
When the validation webhook is called, a scope is created.
* **function naming:** This essentially renames all async functions.
According to best practices, async functions should have the
suffix `Async`.
* **finalizer:** Refactoring of the finalizer logic. Same as with
the controller, the finalizer are now instantiated via dependency injection
in a scope. As soon as a finalization request happens, the finalizer
manager will search for the adequate finalizer and call it.
The new way of registering finalizer is via the `IFinalizerManager`
to attach a finalizer to an entity.
* **controller:** Refactoring of the whole controller instantation.
This removes the `ResourceControllerBase` class. Please migrate to
the new interface `IResourceController`. The basic idea is to provide
scoped access like asp.net api controller. ALL non abstract classes
that implement that interface are registered as controllers on startup.
Whenever an event for a resource happens, a dependency injection
scope is created and the controller is called with the specific action.
There is no need for a base class anymore.