Action/Bridge/Connector Config Breaks in > 5.3.0 about emqx HOT 5 OPEN

Hello,

It might be related to this PR #11032 @zhongwencool could you please take a look?

This pr was released in 5.1.

from emqx.

Hello,

It might be related to this PR #11032
@zhongwencool could you please take a look?

from emqx.

@KazW

It looks like a compatibility issue between 5.3.0 data integration schema and 5.4.1.
I noticed that you are trying to override the http integration url with environment variable EMQX_CONNECTORS__HTTP__MQTT_MESSAGE__URL
But there were no EMQX_BRIDGE__... in the 5.3.0 run?

Could you share your base config in 5.3 with regards to the http/webhook data integration?

from emqx.

@zmstone

The URL needed to be set in both places, otherwise the flow page said that the flow was connected to a deleted action.

The EMQX_BRIDGE__ settings make it into the config map, so they are part of the ENV when I did the 5.3.0 run, but there is no log line for them. However, the config breaks if it's missing.

Aside from authn/authz/listener sections, these are all the actions/bridges/connectors/rules in the config.

emqxConfig:
  EMQX_ACTIONS__HTTP__MQTT_MESSAGE__CONNECTOR: "mqtt_message"
  EMQX_BRIDGES__WEBHOOK__MQTT_MESSAGE__URL: "http://mqtt-api-host.mqtt-namespace/message"
  EMQX_CONNECTORS__HTTP__MQTT_MESSAGE__URL: "http://mqtt-api-host.mqtt-namespace/message"
  EMQX_ACTIONS__HTTP__MQTT_EVENT__CONNECTOR: "mqtt_event"
  EMQX_BRIDGES__WEBHOOK__MQTT_EVENT__URL: "http://mqtt-api-host.mqtt-namespace/event"
  EMQX_CONNECTORS__HTTP__MQTT_EVENT__URL: "http://mqtt-api-host.mqtt-namespace/event"
  EMQX_RULE_ENGINE__RULES__MQTT_MESSAGE__ACTIONS: '[\"webhook:mqtt_message\"]'
  EMQX_RULE_ENGINE__RULES__MQTT_MESSAGE__SQL: |-
    SELECT
        id,
        clientid,
        username,
        base64_encode(payload) AS payload,
        peerhost,
        topic,
        qos,
        flags,
        headers,
        pub_props,
        timestamp,
        publish_received_at,
        node
    FROM
        \"#\"
  EMQX_RULE_ENGINE__RULES__MQTT_EVENT__ACTIONS: '[\"webhook:mqtt_event\"]'
  EMQX_RULE_ENGINE__RULES__MQTT_EVENT__SQL: |-
    SELECT
      *
    FROM
      \"$events/message_delivered\",
      \"$events/message_acked\",
      \"$events/message_dropped\",
      \"$events/client_connected\",
      \"$events/client_disconnected\",
      \"$events/client_connack\",
      \"$events/client_check_authz_complete\",
      \"$events/session_subscribed\",
      \"$events/session_unsubscribed\",
      \"$events/delivery_dropped\"

from emqx.

Hi @KazW
Thank you for your reply.
The reason I'm asking is: it seems odd that you have EMQX_BRIDGES__ and EMQX_ACTIONS__ at the same time.

Since 5.3, bridges are being gradually refactored to action + connector.
For backward compatibility, if bridge is configured, EMQX splits it into two parts (action and connector) when loading the configs.

The behavior is undefined when both bridge and action + connector exist for the same webhook integration.
Maybe it worked in 5.3 by accident, then in 5.4 there is more strict schema check.
The error message provided in your original post #{kind => validation_error,path => "actions.http.mqtt_message.parameters",reason => required_field} hints that the parameters filed is not found: https://www.emqx.io/docs/en/v5.4.1/hocon/#V-actions-S-actions-http-S-http_action-parameters

If you want to keep using the bridge config,
you can follow the config schema here: bridges

If you wish to move to the new action + connector config style,
you can follow the config schema here:
actions
connectors

Note: eventually we will stop publishing documents for bridge, but keep only action and connector.

from emqx.