Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-14857

Implement mock vault

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: current_quarter
    • Component/s: plt
    • Labels:

      Description

      Implement the mock vault and add it to tests to ensure that the general API behavior is the same between the Secrets Manager vault and mock vault.

      The mock vault should first record the input and produce the stubbed output if the user sets it, like how the Secrets Manager client does this for its inputs. Otherwise, it should fall back to its default vault behavior, which is to store secrets in the fake Secrets Manager service stored in memory.

      The easiest way to achieve the default vault behavior this is to embed with another vault, which will be the default implementation. The vault can be the actual Secrets Manager vault implementation backed by a mock Secrets Manager client. That way, the client will use the in-memory fake Secrest Manager storage cache rather than actual Secrets Manager and the vault won't have to be re-implemented.

      The mock should be tested against the common vault test cases to ensure that the default behavior is as expected.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kimberly.tao Kim Tao
              Reporter:
              kimberly.tao Kim Tao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: