search

onedr0p / home-ops

Wife approved HomeOps driven by Kubernetes and GitOps using Flux
https://onedr0p.github.io/home-ops/
Do What The F*ck You Want To Public License
1.98k stars 179 forks source link

fix(container): update public.ecr.aws/emqx/emqx ( 5.7.1 → 5.7.2 ) #7972

Closed bot-ross[bot] closed 2 months ago

bot-ross[bot] commented 2 months ago

This PR contains the following updates:

Package Update Change
public.ecr.aws/emqx/emqx (source) patch 5.7.1 -> 5.7.2

Release Notes

emqx/emqx (public.ecr.aws/emqx/emqx) ### [`v5.7.2`](https://togithub.com/emqx/emqx/releases/tag/v5.7.2): EMQX v5.7.2 [Compare Source](https://togithub.com/emqx/emqx/compare/v5.7.1...v5.7.2) ##### Enhancements - [#​13317](https://togithub.com/emqx/emqx/pull/13317) Added a new per-authorization source metric type: `ignore`. This metric increments when an authorization source attempts to authorize a request but encounters scenarios where the authorizer is not applicable or encounters an error, resulting in an undecidable outcome. - [#​13336](https://togithub.com/emqx/emqx/pull/13336) Added functionality to initialize authentication data in the built-in database of an empty EMQX node or cluster using a bootstrap file in CSV or JSON format. This feature introduces new configuration entries, `bootstrap_file` and `bootstrap_type`. - [#​13348](https://togithub.com/emqx/emqx/pull/13348) Added a new field `payload_encode` in the log configuration to determine the format of the payload in the log data. - [#​13436](https://togithub.com/emqx/emqx/pull/13436) Added the option to add custom request headers to JWKS requests. - [#​13507](https://togithub.com/emqx/emqx/pull/13507) Introduced a new built-in function `getenv` in the rule engine and variform expression to facilitate access to environment variables. This function adheres to the following constraints: - Prefix `EMQXVAR_` is added before reading from OS environment variables. For example, `getenv('FOO_BAR')` is to read `EMQXVAR_FOO_BAR`. - These values are immutable once loaded from the OS environment. - [#​13521](https://togithub.com/emqx/emqx/pull/13521) Resolved an issue where LDAP query timeouts could cause the underlying connection to become unusable, potentially causing subsequent queries to return outdated results. The fix ensures the system reconnects automatically in case of a timeout. - [#​13528](https://togithub.com/emqx/emqx/pull/13528) Applied log throttling for the event of unrecoverable errors in data integrations. - [#​13548](https://togithub.com/emqx/emqx/pull/13548) EMQX now can optionally invoke the `on_config_changed/2` callback function when the plugin configuration is updated via the REST API. This callback function is assumed to be exported by the `_app` module. For example, if the plugin name and version are `my_plugin-1.0.0`, then the callback function is assumed to be `my_plugin_app:on_config_changed/2`. - [#​13386](https://togithub.com/emqx/emqx/pull/13386) Added support for initializing a list of banned clients on an empty EMQX node or cluster with a bootstrap file in CSV format. The corresponding config entry to specify the file path is `banned.bootstrap_file`. This file is a CSV file with `,` as its delimiter. The first line of this file must be a header line. All valid headers are listed here: - as :: required - who :: required - by :: optional - reason :: optional - at :: optional - until :: optional See the [Configuration Manual](https://docs.emqx.com/en/enterprise/v@EE_VERSION@/hocon/) for details on each field. Each row in the rest of this file must contain the same number of columns as the header line, and the column can be omitted then its value is `undefined`. ##### Bug Fixes - [#​13222](https://togithub.com/emqx/emqx/pull/13222) Resolved issues with flags checking and error handling associated with the Will message in the `CONNECT` packet. For detailed specifications, refer to: - MQTT-v3.1.1-\[MQTT-3.1.2-13], MQTT-v5.0-\[MQTT-3.1.2-11] - MQTT-v3.1.1-\[MQTT-3.1.2-14], MQTT-v5.0-\[MQTT-3.1.2-12] - MQTT-v3.1.1-\[MQTT-3.1.2-15], MQTT-v5.0-\[MQTT-3.1.2-13] - [#​13307](https://togithub.com/emqx/emqx/pull/13307) Updated `ekka` library to version 0.19.5. This version of `ekka` utilizes `mria` 0.8.8, enhancing auto-heal functionality. Previously, the auto-heal worked only when all core nodes were reachable. This update allows to apply auto-heal once the majority of core nodes are alive. For details, refer to the [Mria PR](https://togithub.com/emqx/mria/pull/180). - [#​13334](https://togithub.com/emqx/emqx/pull/13334) Implemented strict mode checking for the `PasswordFlag` in the MQTT v3.1.1 CONNECT packet to align with protocol specifications. Note: To ensure bug-to-bug compatibility, this check is performed only in strict mode. - [#​13344](https://togithub.com/emqx/emqx/pull/13344) Resolved an issue where the `POST /clients/:clientid/subscribe/bulk` API would not function correctly if the node receiving the API request did not maintain the connection to the specified `clientid`. - [#​13358](https://togithub.com/emqx/emqx/pull/13358) Fixed an issue when the `reason` in the `authn_complete_event` event was incorrectly displayed. - [#​13375](https://togithub.com/emqx/emqx/pull/13375) The value `infinity` has been added as default value to the listener configuration fields `max_conn_rate`, `messages_rate`, and `bytes_rate`. - [#​13382](https://togithub.com/emqx/emqx/pull/13382) Updated the `emqtt` library to version 0.4.14, which resolves an issue preventing `emqtt_pool`s from reusing pools that are in an inconsistent state. - [#​13389](https://togithub.com/emqx/emqx/pull/13389) Fixed an issue where the `Derived Key Length` for `pbkdf2` could be set to a negative integer. - [#​13389](https://togithub.com/emqx/emqx/pull/13389) Fixed an issue where topics in the authorization rules might be parsed incorrectly. - [#​13393](https://togithub.com/emqx/emqx/pull/13393) Fixed an issue where plugin applications failed to restart after a node joined a cluster, resulting in hooks not being properly installed and causing inconsistent states. - [#​13398](https://togithub.com/emqx/emqx/pull/13398) Fixed an issue where ACL rules were incorrectly cleared when reloading the built-in database for authorization using the command line. - [#​13403](https://togithub.com/emqx/emqx/pull/13403) Addressed a security issue where environment variable configuration overrides were inadvertently logging passwords. This fix ensures that passwords present in environment variables are not logged. - [#​13408](https://togithub.com/emqx/emqx/pull/13408) Resolved a `function_clause` crash triggered by authentication attempts with invalid salt or password types. This fix enhances error handling to better manage authentication failures involving incorrect salt or password types. - [#​13419](https://togithub.com/emqx/emqx/pull/13419) Resolved an issue where crash log messages from the `/configs` API were displaying garbled hints. This fix ensures that log messages related to API calls are clear and understandable. - [#​13422](https://togithub.com/emqx/emqx/pull/13422) Fixed an issue where the option `force_shutdown.max_heap_size` could not be set to 0 to disable this tuning. - [#​13442](https://togithub.com/emqx/emqx/pull/13442) Fixed an issue where the health check interval configuration for actions/sources was not being respected. Previously, EMQX ignored the specified health check interval for actions and used the connector's interval instead. The fix ensures that EMQX now correctly uses the health check interval configured for actions/sources, allowing for independent and accurate health monitoring frequencies. - [#​13503](https://togithub.com/emqx/emqx/pull/13503) Fixed an issue where connectors did not adhere to the configured health check interval upon initial startup, requiring an update or restart to apply the correct interval. - [#​13515](https://togithub.com/emqx/emqx/pull/13515) Fixed an issue where the same client could not subscribe to the same exclusive topic when the node was down for some reason. - [#​13527](https://togithub.com/emqx/emqx/pull/13527) Fixed an issue in the Rule Engine where executing a SQL test for the Message Publish event would consistently return no results when a `$bridges/...` source was included in the `FROM` clause. - [#​13541](https://togithub.com/emqx/emqx/pull/13541) Fixed an issue where disabling CRL checks for a listener required a listener restart to take effect. - [#​13552](https://togithub.com/emqx/emqx/pull/13552) Added a startup timeout limit for EMQX plugins with a default timeout of 10 seconds. Before this update, problematic plugins could cause runtime errors during startup, leading to potential issues where the main startup process might hang when EMQX is stopped and restarted. ##### Breaking Changes - [#​12947](https://togithub.com/emqx/emqx/pull/12947) For JWT authentication, a new boolean option `disconnect_after_expire` has been added with default value set to `true`. When enabled, the client will be disconnected after the JWT token expires. Previously, the clients with actual JWTs could connect to the broker and stay connected even after the JWT token expired. Now, the client will be disconnected after the JWT token expires. To preserve the previous behavior, set `disconnect_after_expire` to `false`.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

This PR has been generated by Renovate Bot.

bot-ross[bot] commented 2 months ago 
--- kubernetes/main/apps/database/emqx/cluster Kustomization: flux-system/emqx-cluster EMQX: database/emqx

+++ kubernetes/main/apps/database/emqx/cluster Kustomization: flux-system/emqx-cluster EMQX: database/emqx

@@ -62,13 +62,13 @@

           subPath: init-mqtt.py
       extraVolumes:
       - configMap:
           name: emqx-init-mqtt-configmap
         name: init-mqtt
       replicas: 3
-  image: public.ecr.aws/emqx/emqx:5.7.1
+  image: public.ecr.aws/emqx/emqx:5.7.2
   listenersServiceTemplate:
     metadata:
       annotations:
         io.cilium/lb-ipam-ips: 192.168.42.129
     spec:
       type: LoadBalancer