Disable 6.0 driver FLE compat tests CI

XMLWordPrintableJSON

    • Not Needed
    • 🔵 Done
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      The node-driver 6.0 evergreen project is intended to test compatibility between driver 6.0 with mongodb-client-encryption@latest, to ensure this compatibility is not broken.  

      This CI broke around February 4th (first failing run https://spruce.mongodb.com/version/node_mongodb_native_6.0_cf89a0800d53e9ed8b7dcd9887f7f83d61a5b1e9_498c05a27eb49b5a97c145b11d106576/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC) and is likely related to adopting secrets manager in CI: https://jira.mongodb.org/browse/NODE-5507.

      AC

      • Add a new task to main driver CI that installs the 6.0 driver and runs the FLE integration and unit tests
      • import the 6.0 driver using the test/mongodb.ts consolidated import
        • make sure all test files use the mongodb.ts import (look for "@typescript-eslint/no-restricted-imports")
      • Correct any failures that can be, skip any API incompatibilities by adding a new filter for driver version (read the package.json like in the mongo client encryption filter)
      • Disable this configuration as it's only relevant to v6 and we are adopting a new peer versioning strategy for mongodb-client-encryption with V7 moving forward that will not require testing it with lowest driver version

            Assignee:
            Unassigned
            Reporter:
            Bailey Pearson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: