yuanbiao/emqx
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
16,262 Commits 393 Branches 684 Tags 74 MiB
0adbb0deec
Commit Graph

8107 Commits

Author SHA1 Message Date
zhongwencool
0adbb0deec feat: try to save config when post_config_update failed not in init mfa status 2023-06-15 17:19:11 +08:00
JimMoen
903d8d899e
fix: .js files are required by dashboard as static 
revert parts of 8c1334c421
 2023-06-15 16:10:16 +08:00
firest
c28346d67b chore: bump ecql for obfuscate sensitive data to avoid leakage 2023-06-15 10:35:18 +08:00
Paulo Zulato
36d6350880
Merge pull request #11031 from paulozulato/fix-influx-wrong-username 
fix(influxdb): check authentication
 2023-06-14 14:41:50 -03:00
zhongwencool
41004e86da
Merge pull request #10959 from qzhuyan/dev/william/remove-depre-quic-config 
chore: remove deprecated QUIC listener config
 2023-06-14 23:01:00 +08:00
zhongwencool
bd269e259e
Merge pull request #11047 from zhongwencool/dashboard-listeners-deprecate-enable 
feat: deprecated dashboard.listeners.name.enable
 2023-06-14 22:58:39 +08:00
Serge Tupchii
7882755114 chore: bump cowboy to 2.9.2 
cowboy 2.9.2 uses ranch 1.8.1-emqx that fixes incompatible TLS options
 2023-06-14 17:35:17 +03:00
Serge Tupchii
4425942030 fix(emqx_schema): move tls version gap validation to emqx_schema 2023-06-14 17:29:56 +03:00
Ivan Dyachkov
6d88cd7a20 fix(tls): fix incompatible tls options and issue with tls version gap 2023-06-14 17:29:56 +03:00
Paulo Zulato
a573b9b38c fix(influxdb): check authentication 
Checks authentication on bridge start and get status. Also, handle
authentication error when sending message.

Fixes https://emqx.atlassian.net/browse/EMQX-10213
 2023-06-14 11:27:39 -03:00
zhongwencool
9209e0bed5 test: delete dashboard.listeners.xx.enable 2023-06-14 20:51:17 +08:00
zhongwencool
4b82d4d927 feat: deprecated dashboard.listeners.name.enable 2023-06-14 20:51:17 +08:00
zhongwencool
267053cc35
Merge pull request #11045 from zhongwencool/hide-zones-authn-in-listeners 
feat: hide zone/authn in listeners and remove listeners's authn api
 2023-06-14 20:32:27 +08:00
zhongwencool
f6df52020c test: conf_cli failed with replace 2023-06-14 18:43:41 +08:00
Andrew Mayorov
1beb588207
fix(ft): give more failproof example in README 
Without that `ssl` defaults to being disabled, and interacting
with AWS S3 with such configuration consistently times out.
 2023-06-14 13:15:00 +03:00
zhongwencool
9a0856fd6b fix: authn/authz's keys should be binary 2023-06-14 18:00:36 +08:00
zhongwencool
bd33dcb049 feat: remove zone from /clients api 2023-06-14 17:11:20 +08:00
zhongwencool
121cd9124a chore: improve show_keys output 2023-06-14 15:53:55 +08:00
zhongwencool
7668753f50 feat: hide zone/authn in listeners and remove /listeners/:id/authentication api 2023-06-14 15:17:12 +08:00
JianBo He
80e2c2c955 fix(http): avoid crash if the old sample data dont contain live_connections 
In version 5.1.0, a new metric called "live_connections" was added. However, we try to merge
some data from the Mria disk table, which may include old data formats.

Therefore, maps:get/3 is needed to avoid crashes.
 2023-06-14 15:14:20 +08:00
JianBo He
8ce0380704 chore: bump vsn to e5.1.0-alpha.6 2023-06-14 12:49:02 +08:00
JianBo He
86d3b702d7
Merge pull request #11042 from zhongwencool/max-connections-string 
fix: api_listener crash when setting max_connnections as string
 2023-06-14 12:46:40 +08:00
zhongwencool
feb08b1181 chore: update 11042 changelog 2023-06-14 11:40:20 +08:00
zhongwencool
091c49277f fix: api_listener crash when setting max_connnections as string 2023-06-14 11:26:41 +08:00
JianBo He
26ad06b9ca chore: update changes 2023-06-14 10:49:17 +08:00
JianBo He
c4c32f5032 chore: cover stomp mountpoint tests 2023-06-14 10:49:17 +08:00
JianBo He
4212d90672 fix(stomp): unmount topic prefix in delivering proccess 2023-06-14 10:49:17 +08:00
JianBo He
e3d208f678 fix(gw): close the stomp connections once an error frame occured 
According to the Stomp v1.2 specification:

> The server MAY send ERROR frames if something goes wrong. In this case,
> it MUST then close the connection just after sending the ERROR frame

Additional, fixes the `is_superuser` is not working for all gateways
 2023-06-14 10:49:17 +08:00
zhongwencool
d41a23b7d0
Merge pull request #11036 from zhongwencool/conf-load-cli 
feat: support --replace|merge with conf load
 2023-06-14 10:48:13 +08:00
zhongwencool
7f0f40cb58
Merge pull request #11034 from zhongwencool/mqtt-conf 
feat:  move shared_subscription_strategy from broker to mqtt
 2023-06-14 10:00:38 +08:00
zhongwencool
9b5c7065f2 feat: conf reload support --replace|merge 2023-06-14 09:12:39 +08:00
zhongwencool
095fb040c0 chore: format conf cli usage text 2023-06-14 09:12:39 +08:00
zhongwencool
a8959900d0 feat: support --replace|merge with conf load 2023-06-14 09:12:39 +08:00
zhongwencool
f57ff802e4
Merge pull request #11038 from thalesmg/fix-pulsar-get-status-r51 
fix(pulsar_producer): do not return `disconnected` when checking status (r5.1)
 2023-06-14 08:32:25 +08:00
Thales Macedo Garitezi
25b0e31035 fix(kafka_producer): do not return disconnected when checking status (r5.1) 
Fixes https://emqx.atlassian.net/browse/EMQX-10279

Related: https://github.com/emqx/emqx/pull/11038

Since wolff client has its own replayq that lives outside the management of the buffer
workers, we must not return disconnected status for such bridge: otherwise, the resource
manager will eventually kill the producers and data may be lost.
 2023-06-13 13:54:57 -03:00
Thales Macedo Garitezi
b609792a90 fix(pulsar_producer): do not return disconnected when checking status (r5.1) 
Fixes https://emqx.atlassian.net/browse/EMQX-10278

Since Pulsar client has its own replayq that lives outside the management of the buffer
workers, we must not return disconnected status for such bridge: otherwise, the resource
manager will eventually kill the producers and data may be lost.
 2023-06-13 11:44:45 -03:00
zhongwencool
946de4a303 chore: dialyzer warning 2023-06-13 20:11:49 +08:00
zhongwencool
50041fdddf feat: hide broker rootkey and move broker.shared_subscription_strategy to mqtt.shared_subscription_strategy 2023-06-13 19:35:52 +08:00
zhongwencool
beee35bdea
Merge pull request #11033 from HJianBo/fix-exproto-mountpoint 
feat(exproto): abandon the mountpoint field in AuthenticateRequest
 2023-06-13 19:18:17 +08:00
JianBo He
7afd9d2b06 chore: update changes 2023-06-13 16:38:23 +08:00
JianBo He
7684cefa86 feat(exproto): abandon the mountpoint field in AuthenticateRequest 
This field was introduced in v4.x, but in fact, in 5.0 we have provided
`gateway.exproto.mountpoint` for configuration, so there is no need to override
it through the Authenticate request
 2023-06-13 14:10:14 +08:00
William Yang
8fa743fa22 chore: mark deprecated QUIC listener config for 5.1 2023-06-13 06:00:57 +02:00
zhongwencool
3331af4757 feat: make gateway and slow_subs low level and hide rule_engine 2023-06-13 11:47:38 +08:00
Thales Macedo Garitezi
5ef7102cba fix(listener_mgmt_api): use union member selector fn for better error messages (r5.1) 
Fixes https://emqx.atlassian.net/browse/EMQX-10247
 2023-06-12 16:48:13 -03:00
Thales Macedo Garitezi
73fe671dba test: rm unused var warnings 2023-06-12 15:19:47 -03:00
zhongwencool
58dc042279 chore: bump to e/v5.1.0-alpha.5 2023-06-13 00:06:54 +08:00
Thales Macedo Garitezi
c11011d857
Merge pull request #11024 from thalesmg/pulsar-cosmetic-connecting-check-r51 
feat(pulsar): retry health check a bit before returning (r5.1)
 2023-06-12 13:00:54 -03:00
Thales Macedo Garitezi
741c1f091e fix(pulsar): update pulsar -> 0.8.3 
Fixes https://emqx.atlassian.net/browse/EMQX-10229

See https://github.com/emqx/pulsar-client-erl/pull/59

Fixes a case_clause error that could arise from race conditions.
 2023-06-12 10:29:40 -03:00
Thales Macedo Garitezi
db5d14d5bf feat(pulsar): retry health check a bit before returning (r5.1) 
Fixes https://emqx.atlassian.net/browse/EMQX-10228

This is a cosmetic fix for the Pulsar Producer bridge health check status.

Pulsar connection process is asynchronous, therefore, when a bridge of this type is
created or updated (which is the same as stopping and re-creating it), the immediate
status will be connecting because it’s indeed still connecting.  The bridge will connect
very soon afterwards (assuming there are no true network/config issue), but having to
refresh the UI to see the new status and/or seeing the resource alarm might annoy users.

This workaround adds a few retries to account for that effect to reduce the probability of
seeing the `connecting` state on such happy-paths.
 2023-06-12 10:26:07 -03:00
firest
0ed420f81f fix: obfuscated the value of JWT 2023-06-12 18:01:02 +08:00