Problem/Motivation

There's lots of configuration that references plugins.

Sometimes modules own both the configuration and the plugin (i.e. Field API).

Sometimes not (Views and Field plugins).

If a module providing a field plugin renames or removes it, what happens to all the configuration that references it?

Proposed resolution

Probably needs to be based on #2080823: Create API to discover config entities' soft dependencies and use this to present a confirm form on module uninstall, except you'd also need to be able to update the configuration based on the change.

Remaining tasks

Lots.

User interface changes

Maybe.

API changes

Some.

Postponed until

#2260457: Allow config entities to remove dependent configuration keys when dependencies are deleted due to module uninstall

Comments

catch’s picture

catch’s picture

Component: base system » configuration system
xjm’s picture

Issue tags: +Configuration system, +VDC
moshe weitzman’s picture

Category: Task » Bug report
Priority: Critical » Major

This strikes me as a normal bug, but lets split the difference.

alexpott’s picture

Status: Active » Postponed (maintainer needs more info)

We need to have a actually problem to solve otherwise we're likely to come up with an non ideal solution.

xjm’s picture

Category: Bug report » Task
Issue tags: -beta target +revisit before release

To clarify @alexpott's comment, we will keep this open to watch for issues as we begin to provide upgrades during the beta phase, and revisit before release to see what steps we might need to take.

xjm’s picture

Issue tags: +beta target
xjm’s picture

Status: Postponed (maintainer needs more info) » Postponed
xjm’s picture

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue tags: +minor version target

Per discussion with @alexpott today, this also might be something we end up shipping in 8.1.0.

xjm’s picture

Issue tags: -revisit before release +revisit before release candidate
tim.plunkett’s picture

xjm’s picture

Related issue posptoned to 8.1.x: #1977498: Add version tracking for configuration schema and data

We agreed to keep this issue marked for revisit before RC, since we are far more likely to change e.g. plugins than schemata.

catch’s picture

Title: Updating active configuration based on API changes (i.e. plugins) » Document/test updating active configuration based on API changes (i.e. plugins)
mgifford’s picture

Status: Postponed » Active

Ok, no need to postpone any more.

xjm’s picture

Status: Active » Closed (duplicate)
Issue tags: -revisit before release candidate, -minor version target

Discussed with @catch, @alexpott, @effulgentsia, and @webchick. This can now be closed as a duplicate of #2538108: Add hook_post_update_X() for data value updates to reliably run after data format updates.