Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Description
Currently, we pass the UpgradeExecutionDependencies when creating the upgrade plan and also when creating the schema upgrade client. Its properties are used only partially depending on the use case, essentially making it a container to hold dependencies for multiple purposes. We should find a better way for the client classes to access these dependencies to stop this DTO bloating and preferably remove the need for it entirely.
Hints:
- Context: https://github.com/camunda/camunda-optimize/pull/3430#discussion_r620037374
- Perhaps a dedicated service that encapsulates all of the dependencies so they don't need to be passed as params would be better