fix: align oss readiness updates#67
Conversation
Greptile SummaryThis PR is a broad OSS readiness sweep across the full monorepo — tightening security, correctness, and observability without adding major new features.
Confidence Score: 4/5Safe to merge; the two findings are both non-blocking quality issues with no runtime impact on the happy path. The changes are well-scoped and the critical paths (tenant isolation, auth throttling, idempotency) all look correct. Two issues stand out:
Important Files Changed
|
| from bigrag.ids import uuid7 | ||
| from bigrag.logging import get_logger | ||
| from bigrag.models.auth import AuditLogEntry, AuditLogListResponse | ||
| from bigrag.services.access_log.payload import _safe_metadata |
There was a problem hiding this comment.
Private symbol imported across module boundary
_safe_metadata carries a leading underscore marking it as private to access_log/payload.py. Importing it from outside that module breaks the encapsulation convention and creates a fragile coupling — any internal rename or refactor of the function signature will silently break audit.py. The same pattern exists in access_log/context.py, which is within the same package and more defensible, but audit.py is a peer module. The function should be made public (remove the underscore) and exported via the access_log package's __init__.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
No description provided.