Allow config override directory to be stored outside of Drupal.

Created on 4 January 2019, almost 6 years ago
Updated 10 May 2023, over 1 year ago

Problem/Motivation

Being able to override specified config outside of Drupal would allow API keys and credentials to be moved to a secure and private directory.

My goal is to make it possible to create a config override directory which only contains API keys. This approach would be similar to Key module β†’ but would allow the original YAML config file's data copied over to override directory not require every key be placed in a separate file.

For example, in the Webform module I want to be able to move just the below API keys from webform.settings.yml to a private and secure directory.

# webform.settings.yml
element:
  default_google_maps_api_key: 'MY API_KEY'
  default_algolia_places_app_id: 'MY APP_ID'
  default_algolia_places_api_key: 'MY API_KEY'

Below is example for Search API

# search_api.server.SERVER_ID.yml
backend_config:
 application_id: 'APP ID'
 api_key: 'API Key'

Proposed resolution

Update \Drupal\config_override\SiteConfigOverrides::getSiteConfigOverrideFolder to support absolute paths.

Remaining tasks

  • Write initial patch
  • Get patch approved
  • Fix any broken tests
  • Write additional tests

User interface changes

N/A

API changes

Maybe

Data model changes

N/A

Release notes snippet

Needed

✨ Feature request
Status

Needs review

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States jrockowitz Brooklyn, NY

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024