Epic: Peripheral GDBM Module Migration #155
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference: aethyr/Aethyr#155
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background and Context
The Issues module (
lib/aethyr/core/issues.rb) and News trait (lib/aethyr/core/objects/traits/news.rb) each maintain their own independent GDBM stores, completely separate from theStorageMachine. These stores are not covered by the existing ES dual-write pattern and will remain as GDBM-only dependencies even after the main migration is complete. They must be migrated to ES before GDBM can be fully removed.Additionally,
bin/aethyr_setuponly initializes GDBM stores and must be updated to support ES initialization.Demonstrable Outcome
The Issues module, News trait, and setup utility all work through the ES path when enabled. Their independent GDBM stores are no longer the only persistence option.
Acceptance Criteria
bin/aethyr_setupinitializes ES alongside GDBMrequire 'gdbm'removed fromissues.rbandnews.rb