As a developer, I want to exclude specific Drupal CMI config keys from export, to ensure that API secrets added via the Admin UI are not committed to code.
To be able to do this we are overriding the specific config key provided by Civic Cookie Control, via settings.php. The actual API key is injected into this file at build time using our build processes.
Currently, the Admin UI for this module, prevents further configuration if the API key hasn't been validated.
Propose that if a dummy value is entered via the interface, the remaining config options are still available to edit.
This will allow an authorised user to edit the required settings, for export to CMI.
Needs review
4.4
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.