Module Description
This module detects changes to the configuration system and exports those changes into a configurable directory of your choice. In addition to that it can fire a POST request with parameters to a http service that you configure which can then react to those configuration changes.
Use case
Imagine production servers which are deployed fully automatically and configured securely such that none of the directories are writeable except public and private storage areas.
However, the config sync directory might be outside those writeable areas, which helps to keep an eye on every change to the configuration on live sites. All the configuration is most likely also stored in version control and will be overwritten the next time the site is being deployed.
This is where config_auto_export comes in: if you still allow certain users to make config changes - e.g. to blocks, webforms or views - then you want to get those changes downstream into your version control system as well. This module makes sure that each change gets exported into a temporary directory and fires a http request to a service that you define. This service is not within scope of this module, but it needs to be said: you can configure e.g. a CI tool in a way that it listens to that service and then collects the config changes, pushes them into your version control system and probably also notifies your developers so that they can review the changes and merge them into a master branch.
This way you get to full circle with Drupal's great configuration management, continuous deployment and clients that need to make config changes on live sites.
Use case
Imagine production servers which are deployed fully automatically and configured securely such that none of the directories are writeable except public and private storage areas.
However, the config sync directory might be outside those writeable areas, which helps to keep an eye on every change to the configuration on live sites. All the configuration is most likely also stored in version control and will be overwritten the next time the site is being deployed.
This is where config_auto_export comes in: if you still allow certain users to make config changes - e.g. to blocks, webforms or views - then you want to get those changes downstream into your version control system as well. This module makes sure that each change gets exported into a temporary directory and fires a http request to a service that you define. This service is not within scope of this module, but it needs to be said: you can configure e.g. a CI tool in a way that it listens to that service and then collects the config changes, pushes them into your version control system and probably also notifies your developers so that they can review the changes and merge them into a master branch.
This way you get to full circle with Drupal's great configuration management, continuous deployment and clients that need to make config changes on live sites.
Module Link
Project Usage
156
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module aims to detect changes to the configuration system, export those changes into a configurable directory, and fire a POST request with parameters to a configured http service in order to react to configuration changes.
Data Name
config_auto_export
OPENAI CHATBOT
OPENAI CHATBOT
