Skip to content

Refactor encrypted fields map generator #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

alcaeus
Copy link

@alcaeus alcaeus commented Jun 12, 2025

Refactors the encrypted field map generator and adds a method to generate field maps for all metadata

GromNaN and others added 2 commits June 12, 2025 15:01
…ine#2759)

* Add test document classes from tutorial

https://github.com/mongodb/docs/blob/master/source/includes/qe-tutorials/node/queryable-encryption-tutorial.js

* Create encryption field map

* Create encrypted collection

* Use promoted properties for encrypted document tests

* Revert changes in BaseTestCase

* Rename EncryptionFieldMapTest

* Create Configuration::getDriverOptions() to create the client

* Support class-level #[Encrypt] attribute

* Skip QE tests on non-supported server configuration

* Add documentation on #[Encrypt] attribute

* Add XML mapping for "encrypt" tag

* Create specific xsd type for embedded documents to enable <encrypt> tag

* Fix import class Throwable

* Fix access to $version property before initialization

* Use an enum for query type

* Make getClientEncryption internal

* Improve type of min/max bounds for range queries

* Use getWriteOptions with createEncryptedCollection

* Use random local master key

* Add assertion on non-decrypted data

* Ignore all DOCTRINE_MONGODB_DATABASE phpstan errors

* Baseline phpstan

* Fix CS and skip phpstan issues
@alcaeus alcaeus force-pushed the generate-encrypted-fields-map branch from b9b6e3f to 97801a6 Compare June 13, 2025 07:41
@alcaeus
Copy link
Author

alcaeus commented Jun 13, 2025

Closing in favour of doctrine#2783.

@alcaeus alcaeus closed this Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants