Problem/Motivation

Doing a single config export for REST there is no dependency.

But staging this file will not enable module(s). Depending on supported_format HAL and REST and depending on supported_auth basic_auth and oauth were expected to be enabled.

rest.settings.yml is a 'simple configuration'

Proposed resolution

Make sure the correct module are enabled by adding dependencies?

Remaining tasks

User interface changes

API changes

Comments

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
CreditAttribution: clemens.tolboom commented
Title: Rest config has no dependencies » Importing rest.config.yml does not enable it's modules
dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

Doesn't those entries point

It is kind of problematic if importing configuration changes configuration. Otherwise you should fail validation when the corresponding modules don't exist, or rather fail if these servides
don't exists? How would you ever be able to have a 100% relyable way from the service ID to the module name?

R.Muilwijk’s picture

R.Muilwijk CreditAttribution: R.Muilwijk commented

Maybe look at how field config handles this with additional field types in modules?

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
CreditAttribution: clemens.tolboom commented
Status: Active » Closed (duplicate)
Related issues: +#2308745: Remove rest.settings.yml, use rest_resource config entities

I guess this will be solved through #2308745: Remove rest.settings.yml, use rest_resource config entities