Problem/Motivation
Currently the module does not consider that it can be installed as part of a configuration synchronization, which leads to different issues including not creating an encryption key.
Steps to reproduce
Install the module as part of config synchronization.
Proposed resolution
Consider the $is_synching flag in hook_install.
Remaining tasks
Review
User interface changes
None.
API changes
None.
Data model changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 3257640-6.patch | 7.33 KB | jcnventura |
Comments
Comment #2
hchonovComment #3
thedut commentedHello hchonov,
Thank your for your work on this issue, I will commit it soon !
Comment #4
undertext commentedHi!
I have a related issue when I use this module in combination with the "field_encrypt" module which is set up to use the same encryption profile as dbee.
Steps to reproduce:
1. Configure dbee and field_encrypt modules and export all the configs (drush cex)
2. Try to import new configs on another machine (drush cim)
3. Dbee Encryption profile is created during module installation despite the encryption profile being already a part of the exported config. Config import tries to recreate (remove and add) the same profile later on and fails with an error:
Cannot delete dbee encryption profile because it is the default for the field_encrypt moduleI've updated the patch to skip encryption profile creation during config sync.
Comment #5
jcnventuraNeeded a small re-roll.
Comment #6
jcnventuraNow with bytes!
Comment #7
jcnventura....
Comment #9
jcnventura