Attempting to deploy the config for this module to a site that doesn't already have the module enabled fails with an error:
[error] Drupal\Core\Config\ConfigImporterException: There were errors validating the config synchronization.
Configuration cci_Cloudfront_auto_cache.settings depends on the cci_Cloudfront_auto_cache extension that will not be installed after import. in Drupal\Core\Config\ConfigImporter->vali
date() (line 750 of /var/www/html/web/core/lib/Drupal/Core/Config/ConfigImporter.php).
It appears this module is using some old naming for its configuration. It's also trying to leverage 2 separate settings files (cci_Cloudfront_auto_cache.settings and cci_Cloudfront_cache.settings). Even though the settings files don't explicitly declare any dependencies, it appears Drupal is making some assumptions about dependencies based on the filenames themselves. I think we need to go down to a single settings file and it needs to be named to match the module name.
Fixed
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I added a patch to fix the Config Export & Config Import issue and fix some naming convention.
Patch applied and tested in the below release
https://www.drupal.org/project/cloudfront_cache_path_invalidate/releases... →