aa33fab25c
ci: remove step to update description on docker hub
2022-12-27 19:51:40 +01:00
2ff6ef01f1
Merge pull request #9599 from lafirest/fix/blacklist_default_exp
...
fix(banned): ensure the default expiration time of `banned` is large enough
2022-12-27 17:30:10 +08:00
a78ecc4bb6
Merge pull request #9579 from thalesmg/bugfix-kafka-producer-stop-client-ee50
...
fix(kafka_producer): cleanup client after failing to start producers
2022-12-26 08:59:36 -03:00
81b226a801
Merge pull request #9608 from zmstone/1123-pin-hocon-0.33.0
...
1123 pin hocon 0.33.0
2022-12-26 19:22:21 +08:00
af3f0c9bb0
fix(banned): ensure the default timeout of `banned` is large enough
2022-12-26 10:17:31 +08:00
f93c22045d
fix: non-empty field should not be undefined
2022-12-24 11:41:45 +01:00
269a40a9ea
fix: format psk user lookup fun back to string
2022-12-23 19:22:15 +01:00
1e3b0c3777
Merge pull request #9609 from thalesmg/mqtt-conn-clientid-v50
...
feat(mqtt): add option to customize clientid prefix for egress bridges
2022-12-23 12:31:44 -03:00
d3efb0c0ba
chore: bump app versions
2022-12-23 15:10:16 +01:00
350023e757
fix(config): option only_fill_defaults renamed to make_serializable
2022-12-23 14:27:04 +01:00
35dc75b7ed
feat(mqtt): add option to customize clientid prefix for egress bridges
...
https://emqx.atlassian.net/browse/EMQX-8445
Currently the bridge client’s client ID is prefixed with the resource
ID.
Sometimes it’s useful for users to have control of this prefix,
e.g. prefix based ACL rules in the target broker.
2022-12-23 09:50:26 -03:00
fa7433628c
fix(logs): set password field sensitive for connectors
2022-12-23 12:46:03 +01:00
700c64fcf0
Merge pull request #9607 from id/docs-remove-references-to-jp-readme
...
docs: remove references to README-JP.md
2022-12-23 12:13:57 +01:00
59970272ff
chore: pin hocon 0.33.0
2022-12-23 12:07:36 +01:00
6292d7ec68
refactor: remove dead code
2022-12-23 12:07:36 +01:00
9eb628f94b
docs: remove references to README-JP.md
2022-12-23 09:59:18 +01:00
317dd06d25
Merge pull request #9604 from id/docs-update-readme
...
docs: update readme
2022-12-23 09:56:54 +01:00
d70a6ec477
docs: update README with Erlang/OTP requirements
2022-12-23 09:21:49 +01:00
2855c39fa9
Merge pull request #9560 from lafirest/fix/conf_template_psk
...
fix(psk): add new supported ciphers to the conf template
2022-12-22 18:58:28 +01:00
3ed14fbfee
docs: update readme
...
- remove info about unixodbc, it's relevent for enterprise only atm
- remove references to 4.3
- update info about supported OTP versions
2022-12-22 17:37:49 +01:00
7eebc67f61
Merge pull request #9603 from emqx/50-ci-fix-self-hosted-macos-runners
...
50 ci fix self hosted macos runners
2022-12-22 17:09:42 +01:00
c678770532
Merge pull request #9571 from olcai/improve-mysql-bridge-test
...
fix: infinite recursion in mysql connector and improve mysql EE bridge tests
2022-12-22 15:37:37 +01:00
a1af5742e2
chore: use unique name for temp macos keychain
2022-12-22 15:34:28 +01:00
780d715dfb
ci: issue with linking unixodbc when building OTP on macos arm64
2022-12-22 15:34:28 +01:00
0baeb6866b
Merge pull request #9600 from emqx/1222-fix-brew-install-in-ci
...
ci: make homebrew more conservative
2022-12-22 15:34:06 +01:00
d70135cc08
ci: make homebrew more conservative
2022-12-22 14:34:45 +01:00
188f829592
Merge pull request #9590 from id/ci-use-our-own-setup-beam-fork
...
ci: use our own setup-beam fork
2022-12-22 14:27:38 +01:00
13942f5c49
refactor: rename error return in mysql connector
2022-12-22 10:29:12 +01:00
cc47ce0034
chore: update changes
2022-12-22 10:27:38 +01:00
aab914d65a
test: refactor EE mysql bridge test case
...
Co-authored-by: Thales Macedo Garitezi <thalesmg@gmail.com>
2022-12-22 10:27:38 +01:00
d5a41b801e
chore: update changes
2022-12-22 10:27:38 +01:00
7df24000a0
test: add more EE mysql bridge test cases
2022-12-22 10:27:38 +01:00
23ac426608
fix(emqx_connector): check for key among prepared statements on query
...
An infinite loop was triggered in the mysql connector when a query
used a prepared statement key that was not among the defined prepared
statements on start. We now check that the key is defined among the
prepared statements before recursing. It seems that this bug was never
triggered in any production code flow and simply found while writing
tests.
An error return spell fix is also included as well as a FIXME comment
regarding running mysql:prepare and not distinguishing between
transient failures and syntax errors. Syntax errors should not be
retried.
2022-12-22 10:27:38 +01:00
0599bd7cfc
ci: use our own setup-beam fork
...
https://github.com/erlef/setup-beam/issues/167
2022-12-22 09:15:57 +01:00
f660724bf7
Merge pull request #9582 from lafirest/fix/fix_field_name
...
fix(limiter): change limiter `cache` to `buffer`
2022-12-21 18:12:40 +08:00
9066513bef
Merge pull request #9576 from id/chore-fix-bin-emqx-logging-on-non-tty
...
chore: fix logging in bin/emqx on non-tty
2022-12-21 09:47:00 +01:00
6f3e952edf
fix(psk): add new supported ciphers to the conf template
2022-12-20 22:40:49 +08:00
a8e020af58
fix(limiter): change limiter `cache` to `buffer`
2022-12-20 22:30:52 +08:00
516147ad00
Merge pull request #9581 from zmstone/1219-fix-mqtt-bridge-config
...
1219 fix mqtt bridge config
2022-12-20 14:47:02 +01:00
b5dbfcf280
Merge pull request #9578 from zmstone/1219-fix-shared-sub-sticky
...
1219 fix shared sub sticky
2022-12-20 13:49:59 +01:00
f19d649c11
Merge pull request #9584 from kjellwinblad/kjell/fix_jq_dont_start_port_programs_when_they_are_not_needed
...
fix: do not start jq port programs when they are not needed
2022-12-20 13:47:52 +01:00
75021b376e
fix: do not start jq port programs when they are not needed
...
The jq function in the rule engine uses the jq NIF implementation by
default so there is often no need to start any jq port programs. Before
this commit jq port programs were started anyway. This is fixed by not
starting the jq application (the jq application is started automatically
when the jq port implementation is activated).
2022-12-20 12:10:35 +01:00
4f582c4300
Merge pull request #9583 from zmstone/1220-add-more-pr-template
...
chore: Add more PR templates
2022-12-20 11:28:44 +01:00
ca75322302
chore: Add more PR templates
2022-12-20 09:17:52 +01:00
479e191dcf
refactor: refine worker pool config and doc
...
worker pool is a buffer pool
the description hinted connection pool which is wrong.
2022-12-20 09:02:51 +01:00
71d40c0490
Merge pull request #9534 from thalesmg/fix-influxdb-no-fields-50
...
fix(influxdb): check if fields are empty before sending
2022-12-20 10:43:15 +08:00
da51433dc3
refactor: add default value for eggress remote 'qos' and 'retain'
...
otherwise when updating from dashboard, there is no way to set
'false' for 'retain' because it's a checkbox,
it's either 'true' or 'undefined'
2022-12-20 00:00:31 +01:00
c085ffa0fe
refactor: default mqtt bridgge buffer pool size down to 4
2022-12-19 23:59:46 +01:00
f611cbab45
chore: cap replayq seg size under total size
2022-12-19 23:16:05 +01:00
7242ce426b
fix(kafka_producer): cleanup client after failing to start producers
...
https://emqx.atlassian.net/browse/EMQX-8547
If a Kafka Producer bridge is given bad configuration (e.g.: bad authn
credentials), the Wolff client process is started successfully, as it
does not attempt to connect, but when the producer process is
attempted to be started, it fails (only then the client tries to
connect to Kafka). At this point, an error was thrown, but the
supervised client process remained running.
If the configuration was later fixed and the bridge updated, which
prompted its removal and recreation, the Wolff client would report to
be "already started", so it would never pick up the new (fixed)
configuration, and the producers would perpetually fail to start until
the node would be restarted.
We simply ensure the client is stopped before throwing the error,
unrolling the start-up procedure.
2022-12-19 17:48:40 -03:00
Ivan Dyachkov