Is your feature request related to a problem? Please describe.
The managed elements of a site's configuration can get our of synch for a number of reasons;
security update to core changes the config exported
security update to a contrib module changes the config exported
an admin UI allows users to change the values exported (ie. menu)
Describe the solution you'd like
While we have several processes we can use to get the captured configuration back in sync with what the live version of the site is using, even knowing that the config isn't insync currently requires logging into the live site or looking at a recent clone locally. While several people have access to see the configuration report, it is always falling on developers to notice that the config is out of sync.
By leveraging a status check (similar to Webform's library CDN check of Drupal security updates), we can expose that message in the CMS UI and the Pantheon site audit in the Dashboard.
Is your feature request related to a problem? Please describe.
The managed elements of a site's configuration can get our of synch for a number of reasons;
Describe the solution you'd like
While we have several processes we can use to get the captured configuration back in sync with what the live version of the site is using, even knowing that the config isn't insync currently requires logging into the live site or looking at a recent clone locally. While several people have access to see the configuration report, it is always falling on developers to notice that the config is out of sync.
By leveraging a status check (similar to Webform's library CDN check of Drupal security updates), we can expose that message in the CMS UI and the Pantheon site audit in the Dashboard.
Describe alternatives you've considered
The process for manually exporting the configuration is already documented in https://github.com/cu-uis/cu-starterkit-project/wiki/Building:Configuration-Management.
Additional context
We have also looked at modules like https://www.drupal.org/project/config_patch_gitlab_api to streamline the process of pushing an updated config in the GitLab as well as running https://docs.gitlab.com/ee/ci/pipelines/schedules.html to pull in updates automatically.