Create WT_KEY_PROVIDER mock module for testing purposes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Extensions
    • None
    • Storage Engines - Foundations
    • SE Foundations - 2025-12-05, SE Foundations - 2025-12-19
    • 5

      Context
      After the implementation of WT_KEY_PROVIDER extension interface module, we can create a mock module to test all new code within this project. The mock module should have the capability to:

      • Periodically perform simple key rotations from time-to-time
      • When get_key is called, waits for on_key_update() determining it is persisted.
      • When a key blob is persisted, all calls to load_key and get_key (with correct indication of changes) will be using new key blob

      The mock module should mimic in a simple way on how they would be utilising key provider system.
      E.g.

      • versioning: a version number and compatibility information with other versions, allowing the format to change in the future.
      • identification: e.g. if something akin to salvage were to see this block, it should be able to distinguish it from the WT page formats used for full pages and deltas.
      • UUID: an ID that identifies the active KEK
      • blob of data: The KEK key

      Definition of Done

      • Basic simple rotation and mock module has been created

            Assignee:
            Alex Blekhman
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: