feat(tenant): rebuild lifecycle isolation on current main - #141
Merged
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (31)
📝 WalkthroughWalkthrough테넌트 범위 durable lifecycle 저장 기능을 추가했습니다. PostgreSQL 스키마와 RLS를 tenant-qualified 식별자로 변경했습니다. standalone API 호환성을 유지하고 tenant-aware client, 영속화 헬퍼, 검증 및 격리 테스트를 추가했습니다. Changes테넌트 lifecycle 격리
Estimated code review effort: 4 (Complex) | ~60 minutes Sequence Diagram(s)sequenceDiagram
participant TenantDurableBatchAPIClient
participant ObservationReserver
participant Provider
participant PostgreSQL
participant TenantLifecycleRecorder
TenantDurableBatchAPIClient->>ObservationReserver: observation order 예약
TenantDurableBatchAPIClient->>Provider: lifecycle 요청
Provider-->>TenantDurableBatchAPIClient: provider batch 응답
TenantDurableBatchAPIClient->>PostgreSQL: tenant scope 설정 및 상태 저장
TenantDurableBatchAPIClient->>TenantLifecycleRecorder: tenant scope와 snapshot 기록
Possibly related issues
Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
seonghobae
marked this pull request as ready for review
August 12, 2026 03:24
This was referenced Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Controlled replacement for #53
PR #53 accumulated a long-lived conflicted history against protected
main. A fresh compare against protectedmain2833e5f382e97943c9cde8ea2966c3e694ba5bd8proved that onlyREADME.mdandCHANGELOG.mdoverlap with changes made on protected main since #53's merge base. This replacement therefore starts from the exact current protected head and replays the exact reviewed #53 result blobs for the other 28 tenant-lifecycle paths.Preserved product boundary
The replay preserves #53's host-selected
tenant_scope,TenantDurableBatchAPIClient, tenant-qualified lifecycle persistence/read helpers, tenant-qualified uniqueness/indexes, parameterized transaction-local tenant context, forced default-deny PostgreSQL RLS, package/container schema identity, standalone compatibility, operator/security documentation, and tenant lifecycle tests.README.mdandCHANGELOG.mdare deliberately left at current protected-main content in this first replacement commit rather than copying stale conflict-side blobs. Exact-head CI is expected to identify any current documentation composition required by the preserved tenant contract; that composition will be applied narrowly from current main.No old #53 check, review, approval, generated merge, or stale-base evidence transfers to this PR. No force-push, destructive rebase, conflict-side selection, gate weakening, release action, or central dependency workaround is used.
Replacement proof
2833e5f382e97943c9cde8ea2966c3e694ba5bd8aaeceb1fcd9022f20108606d92808a96ab5644daREADME.mdandCHANGELOG.mdremain authoritative pending exact-head RED evidenceMerge boundary
Keep Draft until exact-head repository CI, security, coverage, required central workflows, review-thread state, tenant-specific PostgreSQL tests, and current-main documentation composition are all validated. Merge only on an unchanged exact head satisfying live rules and zero valid unresolved findings. After replacement equivalence is proven, close #53 as superseded and rebuild each dependent stack boundary from the protected result in dependency order.
Summary by CodeRabbit
새로운 기능
문서
테스트