Whatever you do, don't let this API key get committed!

  drush config:export

Uh-oh…

Description

Best practice is to export your configuration and commit it to your source-code repository.
Best practice is also to avoid committing API keys, secrets, etc.

The credential mask module integrates with the configuration management API and ensures that the configuration keys marked as "sensitive" are not exported, and when configuration is imported, the unmasked configuration is not overridden.

Operation

This module currently has no UI, and is operated entirely via Drush. If anyone would like to contribute their efforts to create an admin UI, that would be welcome.

Commands

credential_mask:add
Mark a config key as sensitive.
credential_mask:del
Remove a config key from the list of masked credentials.
credential_mask:list
List all active configuration properties identified as sensitive.
credential_mask:show-configuration
Show the configuration names and properties currently marked as sensitive.

Version requirements

Drupal core 8.8 or greater
Drush 10 or greater.

Similar modules

Other modules in the configuration-management ecosystem, such as Config split and Config filter may provide similar behaviour, or tools to achieve a similar outcome.

Credential mask

Issues

Automated Drupal 10 compatibility fixesNeeds reviewCode Created over 2 years ago

Automated Drupal 10 compatibility fixes
Needs review
Code
Created over 2 years ago