[meta] Deploying configuration that depends on content

Created on 23 April 2014, about 10 years ago
Updated 28 July 2023, 11 months ago

Problem/Motivation

Quite a number of config things that we have can/do reference content entities:

  • Blocks of Custom Blocks (required, per block instance)
  • Default values of image/file/term/entity reference fields (optional)
  • Aggregator feed blocks (required, per block instance, reference feed ID)
  • Views...

To reproduce this problem in the most "awesome" way that core can offer:

1. Create a new custom block type
2. Create a custom block of that type
3.. Place that block somewhere.

There is now a block config entity that depends on a custom block content entity which depends on a custom block type config entity.

Now, go and deploy this. Good luck.

Proposed resolution

I have no idea :) We have no system in core for syncing content.

Remaining tasks

User interface changes

API changes

🌱 Plan
Status

Active

Version

11.0 πŸ”₯

Component
ConfigurationΒ  β†’

Last updated about 6 hours ago

Created by

πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

Live updates comments and jobs are added and updated live.
  • VDC

    Related to the Views in Drupal Core initiative.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024