51a6f623fd
refactor(ds): Split out bitfield keymapper to a different module
2023-11-08 03:04:19 +01:00
903b3863d1
chore(ps_ds): make persistent session module use new `emqx_ds` APIs
2023-11-08 03:04:19 +01:00
2972bf14ee
refactor(ds): Implement create_generation gen_rpc storage layer call
2023-11-08 03:04:19 +01:00
6d65707d41
refactor(ds): Implement drop_db function
2023-11-08 03:04:19 +01:00
c6a721a7eb
refactor(ds): Passthrough open_db and get_channels to storage layer
2023-11-08 03:04:19 +01:00
59d01dc823
refactor(ds): Implement emqx_ds:open_db
2023-11-08 03:04:19 +01:00
7095cb8583
refactor(ds): Refactor storage layer
2023-11-08 03:04:19 +01:00
c91df2f5cd
refactor(ds): Create a prototype of replication layer
2023-11-08 03:04:19 +01:00
f1454bb57e
feat(ds): learned topic structure
2023-11-08 03:04:19 +01:00
7ab57824dc
chore(ds): change return type of `storage_layer:next/{1,2}`
...
Part of https://emqx.atlassian.net/browse/EMQX-10942
The goal is to help make it clear to the caller of `next` what to do next: if the iterator
should still be used or if no new messages will ever come out of it.
From:
```erlang
-spec next(iterator()) -> {value, binary(), iterator()} | none | {error, closed}.
```
To:
```erlang
-spec next(iterator()) -> {ok, iterator(), [binary()]} | end_of_stream.
-spec next(iterator(), pos_integer()) -> {ok, iterator(), [binary()]} | end_of_stream.
```
2023-11-08 03:04:19 +01:00
03358b77aa
Merge pull request #11886 from savonarola/1106-fix-old-plugin-compatibility
...
fix(plugins): fix backward compatibility
2023-11-08 01:43:04 +02:00
917809205b
Merge pull request #11895 from thalesmg/tag-e531-alpha4-r53-20231107
...
chore: prepare to tag `e5.3.1-alpha.4`
2023-11-07 13:53:00 -03:00
75704513d8
fix(plugins): fix backward compatibility
2023-11-07 19:06:37 +03:00
c4c9d7ceb3
chore: prepara to tag `e5.3.1-alpha.4`
2023-11-07 13:04:46 -03:00
b255836cbd
Merge pull request #11890 from thalesmg/fix-kafka-unhealthy-r53-20231106
...
fix(resource): take error from action/connector before attempting query
2023-11-07 12:38:57 -03:00
55bf7b31e3
Merge pull request #11770 from igo/patch-1
...
Do not rely on existing user name
2023-11-07 15:31:11 +01:00
3a75bc43fb
Merge pull request #11892 from sstrigler/EMQX-11294-still-many-inaccuracies
...
EMQX 11294 still many inaccuracies
2023-11-07 14:45:37 +01:00
7dcdbc9e51
fix(resource): take error from action/connector before attempting query
...
Fixes https://emqx.atlassian.net/browse/EMQX-11284
Fixes https://emqx.atlassian.net/browse/EMQX-11298
2023-11-07 10:04:04 -03:00
fa740a1927
docs: fix inconsistencies for bridge and connector operations
...
It's only `start` allowed for now. Also fixed some wordings.
2023-11-07 13:58:23 +01:00
f19904d43c
Merge pull request #11877 from zmstone/1102-rename-kafka-to-config
...
Rename connector channel related configs in bridge_v2 to 'parameters'
2023-11-07 13:41:55 +01:00
9742dae30d
Merge pull request #11889 from thalesmg/rename-bridgev2-to-action-apis-r53-20231106
...
chore: rename `bridges_v2` -> `actions` in the public facing APIs
2023-11-07 09:29:06 -03:00
d76ed585b0
chore: correct the application vsn
2023-11-07 11:11:20 +08:00
7bd5579980
chore: fix the documentation generation and example conf checking
2023-11-07 11:09:39 +08:00
4ef156d69e
chore: fix dialyzer warnings
2023-11-07 09:04:50 +08:00
0d9e0bd3fe
chore: fix lot of running bugs
2023-11-07 08:52:10 +08:00
bb8f80f256
test: add test case to pin bridge schema json version 0.1.0
2023-11-06 21:59:36 +01:00
9a26c03a5c
refactor: unify top level field names for bridge v2
2023-11-06 21:45:08 +01:00
ac6ad79029
Merge pull request #11887 from id/1106-test-rule-engine-with-both-profiles
...
ci: test emqx_rule_engine with both ce and ee profiles, use ee by default
2023-11-06 20:16:07 +01:00
2b8cf50a1d
chore: rename `bridges_v2` -> `actions` in the public facing APIs
...
Fixes https://emqx.atlassian.net/browse/EMQX-11330
After feedback from Product team, we should rename `bridges_v2` to `actions` everywhere.
We'll start with the public facing APIs.
- HTTP API
- Hocon schema root key
2023-11-06 15:37:07 -03:00
6af6309301
chore: upgrade to hocon 0.39.19
2023-11-06 19:16:19 +01:00
5f33e09537
Merge pull request #11888 from thalesmg/rm-bridgev2-rule-ref-check-r53-20231106
...
chore: don't disable rule that references non-existent bridge
2023-11-06 13:12:01 -03:00
f17b762596
chore: don't disable rule that references non-existent bridge
...
After feedback from QA, we decided to rollback enforcing the rule to be disabled.
2023-11-06 10:09:14 -03:00
b75b8ef9a9
ci: test emqx_rule_engine with both ce and ee profiles, use ee by default
2023-11-06 13:05:27 +01:00
6f51b9f842
chore: ensure elvis pass
2023-11-06 12:31:54 +08:00
8871738756
chore: ensure emqx_gateway_ocpp tests pass
2023-11-06 12:26:58 +08:00
bea0acd929
fix(ocpp): ensure ocpp gateway options works
2023-11-06 11:56:50 +08:00
5881e34d4e
Merge pull request #11874 from zmstone/1103-validate-bridge-type-and-name-at-entry
...
fix(bridge): do not allow dot in bridge name
2023-11-03 23:04:10 +01:00
0ff4465c78
Merge pull request #11875 from thalesmg/fix-kafka-connecting-r53-20231103
...
fix(kafka_producer): don't return `disconnected` when there are connections issues while starting the bridge
2023-11-03 17:56:00 -03:00
a064eecb68
Merge pull request #11879 from thalesmg/fix-rule-api-downgrade-bridge-r53-20231103
...
fix(rules_api): downgrade bridge id
2023-11-03 17:26:09 -03:00
21a167e1a5
Merge pull request #11873 from zmstone/1103-unhide-nodelay-field
...
fix(kafka): do not hide nodelay field
2023-11-03 20:49:29 +01:00
600747b7e5
fix(bridge): do not allow dot in bridge name
...
also validate name at the API entry
2023-11-03 20:44:57 +01:00
0ee74cd8ae
fix(rules_api): downgrade bridge id
...
Fixes https://emqx.atlassian.net/browse/EMQX-11312
2023-11-03 15:57:13 -03:00
4265ef66cc
fix(kafka_producer): don't return `disconnected` when there are connection issues while starting the bridge
...
Fixes https://emqx.atlassian.net/browse/EMQX-11284
Fixex https://emqx.atlassian.net/browse/EMQX-11298
We don't enforce the connection to be up when starting/creating the bridge, otherwise the
status will be `disconnected` for a possibly transient reason such as network issues or
Kafka broker restart.
Same applies for Azure Event Hub Producer bridge, as they share the same module.
2023-11-03 15:49:36 -03:00
1b56216104
Merge pull request #11878 from kjellwinblad/kjell/shared_con/test/stop_connector_fix
...
test(emqx_bridge_v2_api_SUITE): fix broken test case
2023-11-03 15:46:56 -03:00
77723ada01
Merge pull request #11863 from id/1101-ci-cost-reduction
...
ci cost reduction
2023-11-03 19:09:39 +01:00
dd8085d3a4
test(emqx_bridge_v2_api_SUITE): fix broken test case
2023-11-03 17:49:25 +01:00
8a1b370a5e
Merge pull request #11876 from sstrigler/EMQX-11317-creating-a-bridge-for-a-non-existent-or-non-matching-connector-results-in-a-crash
...
handle errors from pre/post_config_update
2023-11-03 16:26:21 +01:00
953d483c24
Merge pull request #11864 from thalesmg/test-enable-rule-check-deps-r53-20231101
...
fix(rule_engine): don't enable a rule that references non-existent bridge
2023-11-03 11:01:38 -03:00
45bfcea6ae
Merge pull request #11866 from sstrigler/EMQX-11294-e-5-3-1-swaggers-several-misdescriptions-of-ap-is
...
EMQX 11294 swaggers several misdescriptions of APIs
2023-11-03 14:55:46 +01:00
dc11008993
fix(emqx_bridge): handle errors from pre/post_config_update
2023-11-03 14:11:25 +01:00
ieQu1