regiohelden / django-datawatch Goto Github PK

e.g. don't show the link to acknowledge a result if the user doesn't have the permission

will make disabling the signal during tests a lot easier

Add a management command to list all registered check slugs and extend the run management command to support a parameter to run only a single check by slug.

Sometimes it's hard to see which configuration a check is based on.
Therefore we should show some debug information on the check result detail page.

It should be possible to run code when an update gets requested by a user from the webview but not when the check gets updated periodically or by signal triggers.

Checks should not be forced to implement a generate function if a scheduled execution of that check is not used.

Split out the execution backend to support other runtimes than celery

Support some kind of cleanup on each check to remove results of non-existing or unnecessary payloads. There is already a management command to remove results of deleted checks but not for unnecessary payloads on existing checks.

Drop support for Django < 3.2 and Python 3.8
Update requirements for test env

The class based periodic task is not supported in Celery 4

In Result class the permissions is named * acknowledge*
In template detail.html permissions is named * acknowldge*

Current behavior:
An exception is thrown when an acknowledgement already exists on the check result and one tries to acknowledge.

Desired behavior:
If the new acknowledgment ends after the existing one, the existing one should be overridden.
If the new one ends before, the exception should still be thrown.

Introduced in 5d4f48b

Make it easier to test datawatch

Return some response object to be able to store a response value and status

Should prevent issues with renamed model Result

Datawatch should support check not returning any payloads from the generator.
Example

def generate(self):
    try:
        for payload in service.get_data():
            yield payload
    except ServiceException:
        yield

Show appropriate error message

trigger_update cannot distinguish between attributes of the model.

Sometimes you want to skip models with certain attributes or delete old results if a check ends with a specific value.

Add method on the base check, support on the backends and a management command

Handle and log these exception since the business logic of the main application using datawatch should not be affected by issues in datawatch

Be friendly. There should not be a 404 If a check result does not exist anymore after refreshing it.

The link to config should be hidden if the check has no Config class

Add unit tests for the datawatch core and integration tests to check if all custom checks will work as expected.

Add at least a read api to gather statistics on tasks

Save a history of acknowledgements.
e.g. to see when they have been automatically reset.

identifier currently used - id of the Result object.
Fix: use the identifier of Result object

Support filtering by check.