Site and Env to Notifications

Now Site and Env names are included in the notification log entries.
It makes it easier to create alerts on systems that collect logs from multiple sites.

README update

Updated README to include info about Drupal core patching.

Fix a fetch failure

There was a nagging error due to a Drupal core update module bug, so refreshing caused broken module data.

V 2.3.0

A minor feature:

Now the UPDATES_LOG_TEST env variable will be used before the $settings['updates_log_disabled'] to test if we Should run updates_log.

This allows for testing in envs where updates_log is disabled in settings.php.

Bugfix

Occasionally some notifications could go missing.
This is related to the Drupal core problem.
It has a workaround now by delaying the notification until the next cron run.

V 2.2.1

New Feature

• Updates log reporting can be now disabled with $settings['updates_log_disabled'] = TRUE; in settings.php

Fix

• Namespaces in the tests folder

Micro-improvements

• Adjust the module name to match the machine name
• Add co-owner

New features

There are 3 new minor features:

• Site name can be specified in the settings.php by $settings['updates_log_site'];
• Env name can be specified in the settings.php by $settings['updates_log_env'];
• Drupal version is explicitly set in the statistics which allows it to display on the dashboard.

JSON termination improvement

In some environments, logs are embedded into another JSON which makes it difficult to extract Updates Log part.
Now, there is a termination at the end of the JSON: var={json}==.

Fix "Unable to fetch" case

Fixed a nagging problem where Drupal sometimes cannot fetch the updates.
This is a core bug.
https://www.drupal.org/project/drupal/issues/2920285
The update module can get 'stuck' with 'no releases available.