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.

Comments

hchonov created an issue. See original summary.

hchonov’s picture

StatusFileSize
new6.42 KB
thedut’s picture

Hello hchonov,

Thank your for your work on this issue, I will commit it soon !

undertext’s picture

StatusFileSize
new7.37 KB

Hi!
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 module

I've updated the patch to skip encryption profile creation during config sync.

jcnventura’s picture

StatusFileSize
new0 bytes

Needed a small re-roll.

jcnventura’s picture

StatusFileSize
new0 bytes

Now with bytes!

jcnventura’s picture

StatusFileSize
new7.33 KB

....

  • 8261521 committed on 8.x-2.x
    Issue #3257640 by jcnventura, hchonov, undertext: Respect is_syncing in...
jcnventura’s picture

Title: Respect is_synching in hook_install » Respect is_syncing in hook_install
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.