#24475: Add a new testconnections management command
-------------------------------------+-------------------------------------
Reporter: gannetson | Owner:
| alexmorozov
Type: New feature | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by alexmorozov):
@shaib, the whole "checks" framework seems to me to be a registry of
various checks of "system health". Remote dependencies are (for me) the
perfect fit for that. Introducing another command seems to be an real
cognitive overhead.
As for the "remote" connections - I'm quite fine with that, it would help
a lot on deploy. Though such kind of checks surely should be warnings, not
errors.
@timgraham, speaking of starting this as a separate project - I'm not sure
there's an easy way to register those tests as 'checks', while having the
check framework skipping them for the 'common' run. And implementing a
separate 'remote checks' registry (mostly copy-pasting the checks' code)
looks like a total mess for me.
If we could mark some checks tags to be skipped at the plain run (more
generic way of that "deploy" thing), would it be of help?
--
Ticket URL: <https://code.djangoproject.com/ticket/24475#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.c038e71d904c0231d86e7edba4ee7beb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
