lagoon_logs 3.1.0

Fixes a "Circular reference detected" error on Drupal 11.4 and makes uid always an integer in shipped logs, so Elasticsearch/OpenSearch indices map it consistently. Now requires Drupal 10.2 or later.

Contributors (3)

almunnings, dan2k3k4, jonhattan

Changelog

Issues: 3 issues resolved.

Changes since 3.0.1 (compare):

Bug

• #3612134: Drupal 11.4 Circular reference detected
• #3612135: uid is sent as string or int, causing Elasticsearch/OpenSearch mapping conflicts

Feature

• #3563505: Use #config_target and get alerted if 'disable' is overridden in settings.php

Misc

• Require Drupal 10.2 or later for #config_target support
• Added GitLab CI, unit and kernel tests; coding standards cleanup

API changes

• LagoonLogsLoggerFactory has been removed; the logger service is now autowired.
• LagoonLogsLogger constructor arguments changed. The constants LAGOON_LOGS_DEFAULT_SAFE_BRANCH and LAGOON_LOGS_DEFAULT_LAGOON_PROJECT moved to LagoonLogsLogger.

Upgrade notes

Indices already created with uid mapped as text keep that mapping until they roll over or are reindexed.