[DRIVERS-2589] Enable QEv2 tests on Serverless Created: 29/Mar/23  Updated: 21/Aug/23

Status: Implementing
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kevin Albertson Assignee: Kevin Albertson
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Gantt Dependency
has to be done after DRIVERS-2435 Update libmongocrypt payloads to new ... Closed
Issue split
split to CXX-2691 Enable QEv2 tests on Serverless Backlog
split to CDRIVER-4642 Enable QEv2 tests on Serverless Blocked
split to CSHARP-4654 Enable QEv2 tests on Serverless Closed
split to GODRIVER-2848 Enable QEv2 tests on Serverless Closed
split to MOTOR-1134 Enable QEv2 tests on Serverless Closed
split to NODE-5288 Enable QEv2 tests on Serverless Closed
split to PHPLIB-1133 Enable QEv2 tests on Serverless Closed
split to PYTHON-3714 Enable QEv2 tests on Serverless Closed
split to RUBY-3262 Enable QEv2 tests on Serverless Closed
split to RUST-1654 Enable QEv2 tests on Serverless Closed
split to JAVA-4964 Enable QEv2 tests on Serverless Backlog
Driver Changes: Needed
Downstream Changes Summary:

Queryable Encryption tests no longer need to be skipped against MongoDB Serverless.

Engineering Lead: Kevin Albertson Kevin Albertson
Start date:
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4642 Blocked
CXX-2691 Backlog
CSHARP-4654 Done 2.20.0
GODRIVER-2848 Fixed 1.12.0
JAVA-4964 Backlog
NODE-5288 Done 5.7.0
MOTOR-1134 Duplicate
PYTHON-3714 Fixed 4.7
PHPLIB-1133 Fixed 1.16.0
RUBY-3262 Fixed 2.19.0
RUST-1654 Fixed 2.8.0

 Description   

Summary

Once MongoDB Serverless has the Queryable Encryption v2 (QEv2) protocol enabled, tests added in DRIVERS-2435 can be run against MongoDB Serverless.

This depends on MongoDB Serverless upgrading the backing servers to apply SERVER-69563, or having MongoDB Serverless enable the feature flag.

Motivation

Who is the affected end user?

MongoDB Serverless users wanting to use Queryable Encryption.

How does this affect the end user?

Tests may identify unexpected behavior or bugs when using Queryable Encryption with MongoDB Serverless.

How likely is it that this problem or use case will occur?

Not sure.

If the problem does occur, what are the consequences and how severe are they?

Not sure.

Is this issue urgent?

Yes? I expect this is needed before Queryable Encryption becomes Generally Available.

Is this ticket required by a downstream team?

No?

Is this ticket only for tests?

Yes.

Acceptance Criteria

Queryable Encryption specification tests must run against MongoDB Serverless.



 Comments   
Comment by Githook User [ 07/Jun/23 ]

Author:

{'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}

Message: DRIVERS-2589 Enable QEv2 tests on Serverless (#1420)

  • remove Serverless skips from Queryable Encryption prose tests
Comment by Githook User [ 31/Mar/23 ]

Author:

{'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}

Message: DRIVERS-2435 replace `fle2-` tests with `fle2v2-` tests (#1391)

  • add `serverless: forbid` to fle2v2 tests

This will be reverted in DRIVERS-2589

  • add fle2v2 tests

The fle2v2 tests are copies of fle2-* tests
The expected payloads have been updated.
deleteTokens have been removed from the expectations.

  • bump minServerVersion to 7.0.0
  • note that libmongocrypt 1.8.0 is required for fle2v2 tests
  • remove fle2-* tests
  • require server 7.0 for QE prose tests
Generated at Thu Feb 08 08:25:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.