Skip to main content

Gotchas: hbf-data-manager

Package-specific non-obvious patterns and pitfalls. Loaded on demand when working on this package.

  • Dual-guard setup: HBFGuard on read endpoints (calls hbf-core /users/me), DMJwtGuard on delete endpoints (local HS256, DM_AUTH_JWT_SECRET). The DM JWT issuer is hbf-core via DataManagerClient — not hbf-data-retention.
  • No dead-letter queue: Messages failing all 3 retries are silently dropped. Source has a // TODO: Consider adding DLQ comment.
  • Kafka topic name mismatch with hbf-bot: hbf-data-manager defaults to interaction-metadata; hbf-bot defaults to hbf.interaction.metadata. Both are env-configurable via KAFKA_TOPICS — must match in deployment config.