⬆️ Update emqx/emqx to v5.8.0 #110
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependencies
WalkthroughThe change involves updating the EMQX version in the Dockerfile from Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Docker
participant EMQX
User->>Docker: Build Image
Docker->>EMQX: Pull v5.8.0
EMQX-->>Docker: Send Image
Docker-->>User: Image Ready
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- emqx/Dockerfile (1 hunks)
Additional comments not posted (1)
emqx/Dockerfile (1)
10-10: LGTM! But verify compatibility with the new version.The
EMQX_VERSIONargument is correctly updated fromv5.7.2tov5.8.0. Ensure that the new version is compatible with the rest of the system and does not introduce any breaking changes.The code changes are approved.
Run the following script to verify the compatibility of the new version:
This PR contains the following updates:
v5.7.2->v5.8.0Release Notes
emqx/emqx (emqx/emqx)
v5.8.0: EMQX v5.8.0Compare Source
Enhancements
Core MQTT Functionality
debugtowarning. The log messagesocket_receive_paused_by_rate_limitis throttled to avoid excessive logging.Authentication and Authorization
#12418 Enhanced JWT authentication to support claims verification using a list of objects:
Expected values are now treated as templates, consistent with other authenticators, allowing for arbitrary expressions such as
${username}and${clientid}. Previousy, only fixed"${username}""${clientid}"values were supported for interpolation.Improved the documentation for the
verify_claimsparameter.#13229 Added support for
${cert_pem}placeholder in authentication templates.#13534 Added trace logging to indicate when the superuser bypasses the authorization check.
Data Integrations
#13144 Changed the log level to
warningand added throttling for the log messagedata_bridge_buffer_overflowwhen bridge buffers overflow and messages are dropped. Previously, these events were logged at theinfolevel and were not visible with the default log settings.#13492 Enhanced the
GET /connectorsandGET /connectors/:idAPIs to include lists of actions and sources that depend on a specific connector. Additionally, theGET /actions,GET /sources,GET /actions/:id, andGET /sources/:idAPIs now return the list of rules associated with a specific action or source.#13505 Added the ability to filter rules in the HTTP API based on the IDs of data integration actions or sources used.
#13506 Introduced the
peernamefield to all rule engine events that already include thepeerhostfield. Thepeernamefield is a string formatted asIP:PORT.#13516 Added a
direct_dispatchargument to therepublishaction.When
direct_dispatchis set totrue(or rendered astruefrom template) the message is dispatched directly to subscribers. This feature helps prevent the triggering of additional rules or the recursive activation of the same rule.#13573 Introduced
client_attrsto the SQL context for client connectivity events and the messagepublishevent.Users can now access client attributes within rule SQL statements, such as
SELECT client_attrs.attr1 AS attribute1, and utilize${attribute1}in data integration actions.#13640 Added two new SQL functions for rules:
coalesce/2andcoalesce_ne/2.These functions simplify handling null values in rule SQL expressions. For instance, instead of using:
you can now write a more concise expression:
SELECT coalesce(payload.path.to.value, 0) AS my_value.Operations
#13202 Introduced the
emqx ctl conf cluster_sync fixcommand to address cluster configuration inconsistencies. This command synchronizes the configuration of all nodes with the configuration of the node that has the highesttnx_id, ensuring consistency across the cluster.#13250 Added a new value for
cluster.discovery_strategy:singleton. By choosing this option, there will be effectively no clustering, and the node will reject connection attempts to and from other nodes.#13370 Added a new version of
wildcard_optimizedstorage layout for durable storage, offering the following improvements:The new layout does not have an inherent latency.
MQTT messages are serialized into a more space-efficient format.
#13524 Added the
emqx ctl exclusiveCLI interface to manage exclusive topics more effectively. It allows administrators to better manage and troubleshoot exclusive topic subscriptions, ensuring that subscription states are accurately reflected and preventing unexpected failures.#13597 Added thin wrapper functions for plugins to store and manage the certificate files used by the plugins themselves. This fix prevents plugin certificates from being inadvertently deleted by the certificate garbage collection (GC) function.
#13626 Added a new command
emqx ctl listeners enable <Identifier> <Bool>to enable/disable a listener.#13493 Upgraded the RPC library
gen_rpcto version 3.4.0. This update changes the default RPC server socket option fromtruetoactive-100, which introduces back-pressure to peer nodes when the RPC server experiences heavy load.#13665 Added a new metric
emqx_actions_countto the prometheus endpoint. It contains the number of all actions added by all rules, including Republish actions and Console Output actions.Bug Fixes
Core MQTT Functionality
#12944 Fixed an issue that caused a crash when clients with non-UTF8 client IDs attempted to connect with
strict_mode=false.#13006 Improved the validation of retained, delayed, and taken-over session messages to ensure they comply with banned client ID rules implemented through regular expression matching. Previously, certain messages, such as those delayed due to network issues or taken over by another session, could bypass the client ID bans set by regular expressions.
Authentication and Authorization
#13024 Added a default ACL deny rule to reject subscriptions to the
+/#topic pattern. Since EMQX by default rejects subscriptions to#topic, for completeness, it should reject+/#as well.#13040 Improved HTTP authentication:
Content-Typeheader is missing or unrecognized, providing more detailed information.${password}but receives a non-UTF8 password input, leading to better transparency and easier debugging for such scenarios.#13196 Added a limit to the built-in authorization database, restricting the number of Access Control List (ACL) rules per client or user to a default of 100.
#13584 Fixed an issue with creating HTTP authorization that resulted in errors when the HTTP header list was empty.
#13618 Improved the type specifications for the
authorization/sourcesendpoint to provide clearer and more concise error messages.#13624 Fixed an issue in the built-in authorizer where updating rules for a client or user could result in the total number of rules exceeding the
max_ruleslimit.#13678 Made the deletion of an authenticator in the chain an idempotent operation, ensuring that deleting a non-existing authenticator always succeeds.
Data Integrations
#13207 Improved the
republishrule engine action to accurately reflect the success and failure of message publishing. Previously, the success metrics were incremented even when the republish action failed to deliver the message to any subscribers. Now, if the action detects that a message fails to reach any subscriber, the failure metrics are correctly incremented.#13425 Improved the MQTT connector error log messages to provide clearer and more detailed information.
#13589 Fixed an issue where creating a rule with a string
"null"for ID via the HTTP API was allowed, which could lead to an inconsistent configuration.Operations
#13078 Improved validation and error handling in the EMQX Management API to ensure that requests with a JSON body include the
Content-Type: application/jsonheader. If the header is missing for APIs that expect JSON input, the server now correctly responds with a415 Unsupported Media Typestatus code instead of400 Bad Request.#13225 Enhanced security in authentication and authorization APIs by redacting sensitive data such as passwords. Previously, the APIs could return the original password values in responses. With this update, sensitive information is replaced with
******to prevent accidental exposure and protect user credentials.Gateways
Breaking changes
#13080 Updated the default value of the
mqtt.retry_intervalconfiguration from 30 seconds toinfinity.Previously, EMQX would automatically retry message deliveries every 30 seconds by default. With the new default set to
infinity, EMQX will no longer retry message deliveries automatically. This change aligns with MQTT specification standards, which generally do not recommend in-session message delivery retries.We understand that some users rely on the retry feature, so the ability to configure a specific retry interval is still available for backward compatibility.
#13190 Discontinued support for releases on CentOS 7 and Ubuntu 18. EMQX will no longer provide builds for these operating systems due to their end-of-life status.
#13248 Replaced the
builtindurable storage backend with two new backends to provide better flexibility and scalability:builtin_local: A durable storage backend that does not support replication, making it suitable for single-node deployments. This backend is available in both the open-source and enterprise editions of EMQX but is not compatible with multi-node clusters.builtin_raft: A durable storage backend utilizing the Raft consensus algorithm for data replication across multiple nodes. This backend is exclusively available in the enterprise edition of EMQX, providing enhanced data durability and fault tolerance.Additionally, several Prometheus metrics have been renamed to better reflect their functions:
emqx_ds_egress_batcheshas been renamed toemqx_ds_buffer_batchesemqx_ds_egress_batches_retryhas been renamed toemqx_ds_buffer_batches_retryemqx_ds_egress_batches_failedhas been renamed toemqx_ds_buffer_batches_failedemqx_ds_egress_messageshas been renamed toemqx_ds_buffer_messagesemqx_ds_egress_byteshas been renamed toemqx_ds_buffer_bytesemqx_ds_egress_flush_timehas been renamed toemqx_ds_buffer_flush_time#13526 Removed the Core-replicant feature from the Open-Source Edition. Starting from release 5.8, all nodes running the Open-Source Edition will operate in the Core role. This change does not impact Enterprise Edition users, who will continue to have access to the Core-replicant functionality. Additionally, the obsolete
cluster.core_nodesconfiguration parameter has been removed as it is no longer needed.Dashboard Updates: The following features have been removed or restricted in the Open-Source Edition Dashboard:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.