[astarte_data_updater_plant] Added separate AMQP triggers producer configuration (falls back to general AMQP producer settings if unset):
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_HOST - Host for triggers producer connection (no default, falls back to producer host)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_USERNAME - Username for triggers producer (no default, falls back to producer username)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_PASSWORD - Password for triggers producer (no default, falls back to producer password)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_VIRTUAL_HOST - Virtual host for triggers producer (no default, falls back to producer virtual host)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_PORT - Port for triggers producer (no default, falls back to producer port)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_SSL_ENABLED - Enable SSL for triggers producer (no default, falls back to producer SSL setting)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_SSL_CA_FILE - CA certificate file for triggers producer SSL (falls back to producer CA file or bundled cURL certificates)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_SSL_DISABLE_SNI - Disable Server Name Indication for triggers producer (default: false)
DATA_UPDATER_PLANT_AMQP_TRIGGERS_PRODUCER_SSL_CUSTOM_SNI - Custom SNI hostname for triggers producer (falls back to producer host if unset)
[astarte_housekeeping] support network topology replication strategy for the astarte keyspace, with the following env vars:
HOUSEKEEPING_ASTARTE_KEYSPACE_REPLICATION_STRATEGY - Replication strategy for the astarte keyspace: "SimpleStrategy" or "NetworkTopologyStrategy" (default: "SimpleStrategy")
HOUSEKEEPING_ASTARTE_KEYSPACE_REPLICATION_FACTOR - Replication factor when using SimpleStrategy (default: 1)
HOUSEKEEPING_ASTARTE_KEYSPACE_NETWORK_REPLICATION_MAP - Datacenter replication map when using NetworkTopologyStrategy (no default, required when using network strategy)
Added database events handling configuration across all services:
DATABASE_EVENTS_HANDLING_METHOD - Controls how database events are handled: "expose" (via telemetry) or "log" (to logs) (default: "expose")