Problem/Motivation
We want to ensure that any non-production environment never ever sends email to real users and there are handy ways to test emails delivery on development environments.
Acceptance criteria
- Email Reroute module is enabled and configured for all environments
- Production environment has Email Reroute enabled, but ability to reroute emails is disabled in Email Reroute configs
- Fallback to disable emails delivery when Email Reroute is not properly configured on non production environment is implemented
Tech concept
- Install and enable Reroute email module
- Add Reroute email as dependency in domino info.yml file
- Add in composer.json of domino as required module for Reroute email module
- Module should be installed but disabled in configs by default
- For non production environments config should be overridden and rerouting functionality is enabled
- Use Features module to export configs created as a part of this issue into Domino
- Force disable email sending on non production environments if email reroute is not turned on & configured to reroute emails
- Update documentation (README file + update module's description)
Issue fork domino-3312263
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
branimir.juranic commentedComment #3
branimir.juranic commentedComment #4
spleshkaComment #5
spleshkaComment #7
branimir.juranic commentedComment #8
spleshkaThanks Branimir - I've reviewed the MR and left feedback what needs to be improved before the code can hit the main branch. Also, the MR is lacking hook_update_N() to automatically install email_reroute module if it's not installed yet on a project.
Comment #10
pflora commentedHello! I've done the changes requested by #8. I'm still new to Drupal so if there is anything that needs to be done better, please feel free to give me any kind of feedback and i'll try to work on it! :)
Moving this to NR.
Comment #11
spleshkaExcellent job, @pflora, thank you so much! We're nearly there - there are just a few small description issues and a need to update CHANGELOG record. Then the issue is ready to be merged :)
Comment #13
spleshkaGreat job everyone, thanks so much!