PM-34033 - Add individual user seeding to preset pipeline#7304
PM-34033 - Add individual user seeding to preset pipeline#7304theMickster wants to merge 4 commits intomainfrom
Conversation
|
Overall Assessment: APPROVE Adds individual user seeding to the preset pipeline, enabling standalone personal vault accounts without organization overhead. The implementation cleanly extends the existing pipeline architecture with Code Review DetailsNo findings. |
|
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7304 +/- ##
==========================================
+ Coverage 57.89% 57.91% +0.01%
==========================================
Files 2044 2044
Lines 90068 90130 +62
Branches 8011 8020 +9
==========================================
+ Hits 52148 52197 +49
- Misses 36057 36066 +9
- Partials 1863 1867 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|




🎟️ Tracking
PM-34033
📔 Objective
Adds individual user seeding to the preset pipeline — standalone user accounts with no organization, for testing personal vault features (folders, ciphers, favorites) without org overhead. Fixture ciphers and generated ciphers are mutually exclusive (
if/else if), matching the existing org preset pattern. Backward compatible — no changes to existing org preset behavior.🧪 Testing
Expand for testing instructions
Step 1: Seed individual presets
From
util/SeederUtility/:Step 2: Verify login
Login emails come from the preset's
user.emailfield (notowner@<domain>):free-emptyfreeuser@individual.exampleasdfasdfasdfpremium-emptypremuser@individual.exampleasdfasdfasdffree-basicfreeuser@individual.exampleasdfasdfasdfpremium-basicpremuser@individual.exampleasdfasdfasdfStep 3: Validate vault data (free-basic)
Log in as
freeuser@individual.exampleand verify:Step 4: Validate vault data (premium-basic)
Log in as
premuser@individual.exampleand verify:Step 5: Verify backward compatibility
Seed existing org presets and confirm identical behavior: