Problem/Motivation

Create the ConfigEnvironment service for creating and managing config environments.

Proposed resolution

Implement event subscribers for the ConfigTransform API #3047812: Add a Config Transformation event dispatching during config import and export. Each environment corresponds to a new configuration "collection". When config is exported, the config/sync filestorage will show each environment as a subfolder within a "environments" folder, similar to how multilingual config collections are stored.

API changes

  • Provide a ConfigEnvironment service for create, get, set of Environment (config entities)

Data model changes

  • Define the schema for an "environment".
  • Current environment ID will be stored in the State system. (implementation detail of config_environment service)
  • Desired environment ID will be stored in Settings (implementation detail of config_environment service)

User interface changes

None.

Remaining tasks

  1. Move the Config Environment API pieces from the patch in #3028179: Config Environment module (original issue).
  2. Add ConfigEnvironment service to create, set, get current and desired environment ID.

Release notes snippet

CommentFileSizeAuthor
#4 3048860-4.patch32.4 KBbircher

Comments

alexpott created an issue. See original summary.

mpotter’s picture

mpotter commented
Issue summary: View changes
Parent issue: » #3033427: [plan] Add support for environment-specific configuration
Related issues: +#3048860: Create Config Environment API
krzysztof domański’s picture

krzysztof domański
Location Poland
commented
Related issues: -#3048860: Create Config Environment API +#3028179: Config Environment module (original issue)
bircher’s picture

bircher
Location 🇨🇿
commented
StatusFileSize
new 3048860-4.patch32.4 KB

Some work in progress patch.

This can be played with when you enable the new config_environment_switch_test module and go to admin/config/development/configuration/environment.

It has the UI to switch the environment but it doesn't have the environment yet, and also it doesn't properly transform anything yet.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

bircher’s picture

bircher
Location 🇨🇿
commented
Version: 8.9.x-dev » 9.1.x-dev

Discussed with @alexpott. The current issue summary still reflects the required work. Moving 9.1.x as this is not the focus of 8.9.x or 9.0.x

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.