mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-27 09:55:58 +03:00
[GH-ISSUE #1201] Add url endpoint for runign test cases #980
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#980
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @traverseda on GitHub (Jul 28, 2017).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1201
I'm working on getting modoboa integrated with third-party monitoring, using grafana and ansible. Being able to run test cases from the web, and at regular intervals, would be useful.
@tonioo commented on GitHub (Jul 28, 2017):
@traverseda A url endpoint to run tests sounds weird to me... Can't you just a shell script through ssh?
@traverseda commented on GitHub (Jul 28, 2017):
I can do pretty much whatever I want, I am a decent programmer ;p
What that would allow for is one-line integration with a bunch of different monitoring frameworks. Type in the url for your monitoring page, if it changes get an email. A crontab running the testcases at regular intervals and outputting the results to some log-monitoring software would of course be better. But making that information available over the web is a decent best-effort for less complex monitoring systems.
It's also an entry point for DoS attacks, since running test cases would take up a bunch of resources. It would have to be handled carefully.
@kryskool commented on GitHub (Mar 25, 2018):
Hi
It's a worst solution, because modoboa use a lot of component can be test separately, like postfix, amavis, postgresql/mariadb etc, you can stop mdooboa and Postfix dans the database continue to work perfectly.
On modoboa you can only test the first page return status code 200, other status page available in Nginx or Apache2