TYPO3.Flow

[FEATURE] Allow custom custom configuration files in ConfigurationManager

Using the added methods it is possible to register new "types" of
configuration. The set of processing types remains constant, but one
can now e.g. register "Assets" as configuration type and use the
"Settings" processing rule for that. This way it it possible to move
settings for assets into a dedicated file, "Assets.yaml".

The change adds

- resolveConfigurationProcessingType() method
- registerConfigurationType() method
- 2 tests to add a new ConfigurationType
- emitConfigurationManagerReady() to register new ConfigurationTypes during boot

Change-Id: I16b1de8e7c3ec826240c273a87c5e2a095815a86
Resolves: #37854
Releases: master

[FEATURE] Allow split configuration sources

With this change it is possible to allow split configuration sources
when defining a custom configuration type. This allows to use multiple
YAML for a type (when using the bundled YamlSource), which will be
merged together.

Change-Id: Ifb957d182fe8d2f417f5ff1f695215df9666d287
Related: #37854
Releases: 2.0, master

[FEATURE] Allow split configuration sources

With this change it is possible to allow split configuration sources
when defining a custom configuration type. This allows to use multiple
YAML for a type (when using the bundled YamlSource), which will be
merged together.

Change-Id: Ifb957d182fe8d2f417f5ff1f695215df9666d287
Related: #37854
Releases: 2.0, master

[FEATURE] Split configuration sources include non-split default

This change changes the behavior of split configuration sources to
include the default non-prefixed source as a fallback for increased
flexibility, allowing some packages to have split sources and others
to have a single source.

Also a check in the has method is made more strict.

Change-Id: I60c1b40c291b184d22f290c1ffcd02e43fe493a8
Related: #37854
Releases: master, 2.2