mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
29 lines
1.6 KiB
Python
29 lines
1.6 KiB
Python
from django.apps import AppConfig
|
|
|
|
|
|
class FeatureFlagsConfig(AppConfig):
|
|
# AutoField (INT4) matches the legacy insights app default so existing
|
|
# insights_featureflag.id columns stay compatible with the Rust feature-flags
|
|
# service which decodes id as i32.
|
|
default_auto_field = "django.db.models.AutoField"
|
|
name = "products.feature_flags.backend"
|
|
label = "feature_flags"
|
|
|
|
def ready(self) -> None:
|
|
# Connect the flag-cache invalidation receivers at app-population. They used to ride in
|
|
# as an import side effect of a viewset module; with the lazy API router that no longer
|
|
# happens, so a process that never builds the router (celery, temporal, migrate, shell)
|
|
# would stop invalidating the flags cache on flag/cohort/team writes. Wire them here.
|
|
# Same story for the flag activity-log receiver (handle_feature_flag_change), which used to
|
|
# ride in on the viewset import. Flags are mutated in non-web processes (cohort recalculation
|
|
# etc.), so its audit logs must wire here too. It lives in a light activity_logging module
|
|
# because the flag viewset pulls scipy via the dashboard -> error-tracking query runners.
|
|
# flag_version_sync wires here for the same reason: cohort edits happen in
|
|
# non-web processes too, and its version bump must land wherever cohorts save.
|
|
from products.feature_flags.backend import ( # noqa: F401, PLC0415
|
|
activity_logging, # noqa: F401, PLC0415
|
|
flag_version_sync,
|
|
flags_cache,
|
|
local_evaluation,
|
|
)
|