notifications-consumer merge requestshttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests2023-03-31T10:05:36+02:00https://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/109[#93] Draft: Resolve "Move CERN specifics to Config"2023-03-31T10:05:36+02:00Emmanuel Ormancey[#93] Draft: Resolve "Move CERN specifics to Config"Closes #93
Follows https://gitlab.cern.ch/push-notifications/notifications-design/-/issues/55#consumers
Added env:
```
# (CERN) Specific features configuration in Global part: FEATURE_*
FEATURE_SEND_FROM_EGROUP=true
FEATURE_INDICO=tru...Closes #93
Follows https://gitlab.cern.ch/push-notifications/notifications-design/-/issues/55#consumers
Added env:
```
# (CERN) Specific features configuration in Global part: FEATURE_*
FEATURE_SEND_FROM_EGROUP=true
FEATURE_INDICO=true
```Emmanuel OrmanceyEmmanuel Ormanceyhttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/97[HOTFIX] Pin poetry tls error virtualenvs2022-09-26T20:09:52+02:00Caetan Tojeiro Carpente[HOTFIX] Pin poetry tls error virtualenvs`poetry` was updated to v1.2.0 on `pypi`, and it leads on some problems with TLS CA certificates due to the configuration `config virtualenvs.create false`. I pinned the poetry version to the one we were using (1.1.5) and added `certifi`...`poetry` was updated to v1.2.0 on `pypi`, and it leads on some problems with TLS CA certificates due to the configuration `config virtualenvs.create false`. I pinned the poetry version to the one we were using (1.1.5) and added `certifi` dep for none development envs
- https://github.com/python-poetry/poetry/issues/5977
- https://github.com/python-poetry/poetry/issues/1889
closes #79https://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/80[Needs Requirements] Draft: Resolve "Add reply-to to mail header"2022-02-25T14:10:19+01:00Emmanuel Ormancey[Needs Requirements] Draft: Resolve "Add reply-to to mail header"Closes #60
Added new env:
REPLY_TO_EMAIL_PREFIX=notificationsdv|notificationsqa|notifications
REPLY_TO_EMAIL_SUFFIX=dovecotmta.cern.ch
Adds a reply-to hader with channel email rebuilt from
REPLY_TO_EMAIL + channel_slug + level + '@' R...Closes #60
Added new env:
REPLY_TO_EMAIL_PREFIX=notificationsdv|notificationsqa|notifications
REPLY_TO_EMAIL_SUFFIX=dovecotmta.cern.ch
Adds a reply-to hader with channel email rebuilt from
REPLY_TO_EMAIL + channel_slug + level + '@' REPLY_TO_EMAIL_SUFFIXPilotEmmanuel OrmanceyEmmanuel Ormanceyhttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/12[MISSING-REQUIREMENTS][#9]Send-emails-with-TLS2022-02-23T11:54:41+01:00Caetan Tojeiro Carpente[MISSING-REQUIREMENTS][#9]Send-emails-with-TLSI don't have so much knowledge about emailing and protocols, but I think that now the email is sent with TLS since the first hop has TLS header
![imagen_2020-12-10_104342](/uploads/3e18bddca02238287ed71ca24ac76294/imagen_2020-12-10_1043...I don't have so much knowledge about emailing and protocols, but I think that now the email is sent with TLS since the first hop has TLS header
![imagen_2020-12-10_104342](/uploads/3e18bddca02238287ed71ca24ac76294/imagen_2020-12-10_104342.png)
I also checked an email sent without the changes and this header was not present in the first hop.
I also changed the `.env` file to add both ways to develop:
- Sending emails to the console
- Sending emails to the email in the whitelist
It's not the best way to do it but I think is more simple to switch between context like this and not changing them manually. Also if new people join the project I think it will be easier for them to do it and not ask others for the envs for the second case, since in the repo there are only the envs for console emails.
In addition I added to the README a tip for problems with dependencies (since the last commit updated and add some and it was necessary to rebuild the notification-consumers container)
However, if you want to keep it as it is right now I can change it :smile:Carina AntunesIgor JakovljevicCarina Antuneshttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/86Draft: Audit improvements2022-02-15T09:07:38+01:00Carina AntunesDraft: Audit improvementshttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/59Draft: [#45][FALLBACK] Fix broken emails due to big images2021-06-09T15:51:20+02:00Caetan Tojeiro CarpenteDraft: [#45][FALLBACK] Fix broken emails due to big imagesThis MR is a fallback in case of problems with the CSS solution
New MR: https://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/64
closes #45
![image](/uploads/b5ec1bde2de8181530e524cac07c3067/image.png)This MR is a fallback in case of problems with the CSS solution
New MR: https://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/64
closes #45
![image](/uploads/b5ec1bde2de8181530e524cac07c3067/image.png)https://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/57Fix id for dlq processor2021-05-26T10:17:54+02:00Dimitra Chatzichrysoudimitra.chatzichrysou@cern.chFix id for dlq processorCarina AntunesIgor JakovljevicCaetan Tojeiro CarpenteCarina Antuneshttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/25[#21] Refactor ids: use uuid2021-02-26T16:48:06+01:00Emmanuel Ormancey[#21] Refactor ids: use uuid- not much, DB changes for ids as string
Closes #21- not much, DB changes for ids as string
Closes #21PrototypeEmmanuel OrmanceyCarina AntunesEmmanuel Ormanceyhttps://gitlab.cern.ch/push-notifications/notifications-consumer/-/merge_requests/14Draft: Resolve "Create new processor mail-gateway-deadletter"2020-12-11T16:59:55+01:00Igor JakovljevicDraft: Resolve "Create new processor mail-gateway-deadletter"Closes #14Closes #14Prototype