supabase / storage / 42920208702

88%

push

github

feat: wake lifecycle tenants after policy changes (#1693)

## What kind of change does this PR introduce?

feat

## What is the current behavior?
 
Lifecycle policy and versioning changes update the tenant db where
lifecycle state is saved.
Migration 31 enrolls tenants in the central registry if feature is
enabled for a tenant.
However, policy changes themselves do not wake the central tenant
registry.

## What is the new behavior?

After a successful policy PUT/DELETE or versioning enable, make the
tenant due in the central registry.
The wake is best effort and it runs after the tenant db operation.

This only applies to multi-tenant.

## Additional context

A failed wake can delay discovery but if feature is enabled, it will be
woken eventually.
Adding central store for future dispatch: enroll tenants in batches,
claim due tenants and record the result.

Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>

8511 of 10214 branches covered (83.33%)

Branch coverage included in aggregate %.

31 of 31 new or added lines in 3 files covered. (100.0%)

14547 of 16094 relevant lines covered (90.39%)

1357.43 hits per line