Fix: send failure notifications for config init errors #697
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Fixes #696
How I tested this
notification-docker-compose.yml'.token')
Should look like this:
[ { "id": 1, "appid": 2, "message": "Running docker-volume-backup failed with error: main.(*script).init: error creating s3 storage backend: s3.NewStorageBackend: AWS_S3_BUCKET_NAME is defined, but no credentials were provided\n\nLog output of the failed run was:\n\n", "title": "Failure running docker-volume-backup at 2025-12-21T17:39:28Z", "priority": 0, "date": "2025-12-21T17:39:28.49883576Z" } ]