Stream Wrapper for configuration management

Problem/Motivation

Provide a stream wrapper for configuration management.

On containerized hosting environments, the local file system (outside of the public, private, and temp file directories) are typically read only. On large sites with sophisticated clients that have knowledge of Drupal, configuration changes invariably make their way into the site, and the only way to capture those changes is to export the database to a local environment, export the config changes and commit them to the code repository.

With sites that have a lot of content (a common occurrence with enterprise sites), exporting the database in order to do this is a significant task.

It would be great to be able to have a configurable stream wrapper for configuration management that would allow, for example, sending configuration exports to an object store (like Amazon S3).