When exporting the encryptedFieldsMap compare it with model configuration

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Doctrine
    • None
    • PHP Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      When the encrypted fields map in the database is no up-to-date with the current model metatada, this can lead to issues.

      When running the command doctrine:mongodb:dump-encrypted-fields-map, check that the list of encrypted collections and fields is identical between the database and the doctrine metadata.

      Make the command fail when there is a difference, telling to run the schema:update command.

              Assignee:
              Unassigned
              Reporter:
              Jérôme Tamarelle
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: