Skip to content

Replace housekeeping setting with a single one in API

What does this MR do and why?

Instead of three housekeeping options (housekeeping_full_repack_period, housekeeping_gc_period, housekeeping_incremental_repack_period), that are responsible for calling deprecated housekeeping RPCs, now we have a single housekeeping_optimize_repository_period.

It's an alias attribute for housekeeping_optimize_repository_period and all the existing applications will use that value to decided how often OptimizeRepository RPC must be called.

Related issue: #353778 (closed)

Merge request reports