Problem/Motivation
Currently, DeepL API keys are stored in configuration, which can inadvertently be exposed in version-controlled configuration files. This poses a security risk.
Proposed resolution
Integrate the Key module to allow administrators to store DeepL API keys securely using the Key module’s storage system.
Remaining tasks
- Update TMGMT DeepL configuration form to include a Key module field.
- Modify DeepL API client to retrieve the key from the Key module.
- Add dependency on the Key module in tmgmt_deepl.info.yml.
- Update existing documentation and explain how to handle key module
- Update existing unit tests
User interface changes
Add a dropdown field in the TMGMT DeepL configuration form to select a key from the Key module.
API changes
None.
Data model changes
None.
Issue fork tmgmt_deepl-3518088
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
steffenrComment #3
steffenr@emartos: Great feature request. I've added a few more remaining tasks.
Please assign the ticket to yourself, if you want to start working on the issue.
Thanks in advance,
Steffen
Comment #5
steffenrComment #7
steffenrComment #8
steffenr