Contrib.social

Blog - Move certain config to recipe.yml for idempotency

Open on Drupal.org →
Created on 29 August 2024, 4 months ago

Problem/Motivation

Due to the way recipes work, they will throw errors when a different version of config that they want to import exists in the database. Therefor, it is advised to move certain config or parts of config (that are more prone to changing) to the recipe.yml as actions, which will not throw errors.

We should revise the config that this recipe imports and move items to the recipe.yml where needed (e.g. the third party settings).

📌 Task
Status

Active

Component

Track: Blog

Created by

🇧🇪Belgium L_VanDamme

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

Comments & Activities

  • Issue created by @L_VanDamme
  • Status changed to Closed: won't fix about 2 months ago
  • Comment about 2 months ago →
    🇧🇪Belgium L_VanDamme

    I had some discussions about this and the idempotency is still in tact without changing anything.

    There are some changes that could be done like moving the entity displays to config actions, but really it will always be a balancing act, because it is hard to know what might get overridden an what won't. As a current decision, we will only move config to actions if we know for sure it might get overridden (e.g. when another recipe within Drupal CMS would change the config), which is not currently the case for any blog config. If the need arises in the future, separate tickets for the config items would seem to be the best approach.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024