Not possible to install module and populate decision_config_token in one deployment

Created on 16 October 2023, over 1 year ago

When you are trying to install smart_content and a decision config at the same time in a deploymenthook_config_import_steps_alter isn't called so the decison_config_token table doesn't get populated. The previous fix probably assumed the module was already installed? As a workaround I tried to install the module first in an update hook in my own module, however this results in a duplicate entry error as when the config import runs after the update hook both ConfigEntity:importerProcess and ConfigEntity::registerToken are called.

We should check first that the entry doesn't already exist.

πŸ› Bug report
Status

Active

Version

3.1

Component

Code

Created by

achap πŸ‡¦πŸ‡Ί

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024