-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
♻️ enhances emails plugin and 🐛 fixes missing fields ( ⚠️ devops ) #3822 #3835
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3835 +/- ##
========================================
+ Coverage 81.5% 86.7% +5.1%
========================================
Files 883 747 -136
Lines 38876 33017 -5859
Branches 766 393 -373
========================================
- Hits 31721 28646 -3075
+ Misses 6963 4262 -2701
+ Partials 192 109 -83
Flags with carried forward coverage won't be shown. Click here to find out more.
|
e6565f6
to
e58eb70
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot, truly <3 !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
ade9b23
to
94c4d3e
Compare
Code Climate has analyzed commit 503ea4c and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What do these changes do?
Follows up on #3822: emails sent by osparc are classified as spam because some fields are missing. This PR adds missing MIME fields and creates a new entrypoint to test emails directly in the deploy (admin privileges needed). This should help spotting other issues that might be missing in the email server configured in the stack.
There should be one (and one only)
admin
account per deployment (for now, best with mail our common devops mail adress osparcio-devops =at= speag.swiss). No other user (even team members) should have admin privileges. The admin-account will go into the e2e-ops, into the credentials page. This needs to be done upon releasing this PR.Hightlights
email
pluginPOST /email:test
foradmin
to manually test templates and email server (i.e. admin privileges required)Related issue/s
How to test
Checklist
make version-*
make openapi.json