Closed deepthidevaki closed 1 week ago
803 tests 788 :white_check_mark: 12m 48s :stopwatch: 137 suites 15 :zzz: 137 files 0 :x:
Results for commit d956572f.
:recycle: This comment has been updated with latest results.
545 tests 539 :white_check_mark: 1h 35m 4s :stopwatch: 141 suites 6 :zzz: 141 files 0 :x:
Results for commit d956572f.
:recycle: This comment has been updated with latest results.
@npepinpe Sorry, this is a big PR :see_no_evil: But I guess you don't have to go through every change. Please check mainly the renaming for package and module.
Also realized that it will be a pain to backport any bug fixes after this :sob:
💭
dynamic.configuration
is quite long 😄 I would've just named itcluster.config
or something 🤷 After all, most classes after are just calledClusterConfiguration
something. Plus, the artifact is calledzeebe-cluster-configuration
(could be shortened tozeebe-cluster-config
). Not a big deal though, and I can't articulate a better argument, so it's fine.
Done. Renamed to dynamic.config
.
💭 I think we may want a topology listener interface in the future for consumers who only care about topology updates, and not more general config, but it's still too early to say.
It might be useful. Let's add it when it is needed.
Rebasing on main.
Description
We decided to add configurations that can be changed dynamically to the cluster topology and make use of the same infrastructure to apply changes in a systematic way. Hence the name
topology
orClusterTopology
is not meaningful anymore. This PR renames most of the references to topology toconfiguration
orClusterConfiguration
.topology
is renamed todynamic.configuration
dynamic-config
The protobuf messages are not renamed to minimize the impact in this PR. This will be done in a follow up. The gateway rest API responses are also untouched.
Related issues
closes #18032