1ba66fc722
docs: /trace returns list not single trace
2022-12-05 11:50:52 +01:00
f8dd8d652d
docs: add swagger error codes for /trace/:name/[log|download]
2022-12-05 11:50:52 +01:00
9100b13db6
docs: fix schema for /trace/:name/log
2022-12-05 11:50:52 +01:00
28fc2b9ee9
fix(mgmt_api): add missing error codes in schema
2022-12-01 12:20:11 +01:00
311e4cd583
Merge pull request #9440 from zmstone/1128-chore-sync-release-branch-back-to-master
...
1128 chore sync release branch back to master
2022-11-29 11:47:01 +01:00
77341e7a3c
chore: bump app versions
2022-11-28 21:06:33 +01:00
2582c1713e
fix: emqx_topic:join/1 instead of filename:join/1
...
filename:join/1 doesn't work on Windows for joining a topic. We now use
emqx_topic:join/1 instead.
2022-11-28 11:00:18 +01:00
95faf56077
feat: remove $queue in favor of $shared
...
This commit removes support for setting shared subscriptions with the
non-standard $queue feature. Shared subscriptions is now part of the MQTT
spec (using $shared) and we will only support that from now on.
2022-11-28 11:00:18 +01:00
6ee475d9b1
fix(emqx_authz_api_mnesia): return the right matchers
2022-11-24 20:32:00 +01:00
edb35c08a8
chore: refactor ms2qs function type
2022-11-24 20:14:33 +01:00
9786a6c267
refactor(mgmt): convert fuzzy filter func to named func
2022-11-24 20:14:33 +01:00
6d9e1e0d7a
test(mgmt): cover emqx_mgmt_api:cluster_query
2022-11-24 20:14:33 +01:00
b9c5a5f822
fix(delayed): return correct node name
2022-11-24 20:14:33 +01:00
79a2682fd3
chore: improve the no-conditions query
2022-11-24 20:14:33 +01:00
8a0c468b01
test: refine tests for lots of List HTTP API
2022-11-24 20:14:33 +01:00
09958d9a33
chore: fix diaylzer warnings
2022-11-24 20:14:33 +01:00
8f7337c9d2
chore: return undefined fuzzy searching func
2022-11-24 20:14:33 +01:00
28d391f26c
fix(mgmt): collect total number in node_query/cluster_query
2022-11-24 20:14:33 +01:00
1fe9c105aa
refactor(mgmt): smplify the node_query/cluster_query implementation
2022-11-24 20:14:33 +01:00
08121e7df6
fix(mgmt): optimize the speed of query tail pages
...
In the previous, when you query the tail pages, all the front of rows
will be queried out and formatted. It greatly hurts the speed of query.
Currently, we only format the final result rows. i.e, the query for the
last page of data will be 10x faster.
2022-11-24 20:14:33 +01:00
afcb33aa20
feat: support publish with properties
2022-11-23 17:04:35 +01:00
acef85e11a
test: initialize clients in test setup, teardown after test
2022-11-23 17:03:43 +01:00
65820eb943
fix: can't get default raw config
2022-11-18 15:07:23 +08:00
d9e7d36580
chore: bump version && update changes
2022-11-14 09:45:38 +08:00
2f4b2ba405
fix(mgmt_api): Convert only what is needed when parsing subscription information
2022-11-14 09:44:22 +08:00
30d9143b0e
Merge pull request #9310 from sstrigler/fix-configs-api-for-bad-nodes
...
fix(emqx_mgmt_api_configs): use 'node' query paramter if given
2022-11-08 18:10:43 +01:00
ebaba0c2b1
fix: Revert "feat(banned): clean retained/delayed data when client is banned"
...
This reverts commit 69701ff578
2022-11-08 11:36:11 +08:00
1fb441dd9e
test: add tests for 'configs?node'
2022-11-07 14:12:21 +01:00
104b1a63d9
test: pass down Opts in request_api/X
2022-11-07 14:12:21 +01:00
8b10b78bce
fix(emqx_mgmt_api_configs): use 'node' query paramter if given
...
also fix result in error case - be compliant to schema and also return correct
http status code
2022-11-07 14:12:20 +01:00
14c8b5ebb1
fix(mgmt): Ensure the CLI will not create useless atom
...
The log level, the log handler id and the listener id all of them already exist,
so it's better to avoid the user create a useless atom by mistake input
2022-11-02 16:50:43 +08:00
5886db08e0
Merge pull request #9279 from lafirest/fix/binary_to_atom
...
fix: use binary_to_existing_atom to replace some risky binary_to_atom
2022-11-02 10:57:05 +08:00
60492615ba
fix(API): Ensure that the node name is known
2022-11-01 17:28:34 +08:00
198ddda8bc
docs(status_api): add remark about feature introduction versions
2022-10-31 14:10:09 -03:00
12addc2118
Merge pull request #9230 from thalesmg/status-endpoint-alias-50
...
feat(mgmt): add alias endpoint for health check
2022-10-31 10:22:17 -03:00
18235a7125
chore: update emqx_managment bpapi.versions
2022-10-28 09:16:05 +08:00
af79e652da
chore: clear dialyzer warning.
2022-10-28 09:16:05 +08:00
ea95f792e0
refactor: multicall node_info to improve /node speed
2022-10-28 09:14:33 +08:00
d0ca79fc9e
feat(mgmt): add alias endpoint for health check
...
This allow use to reference `/status` in the API documentation without
manually editing the `swagger.json` file.
2022-10-27 13:20:04 -03:00
c72f3a0ae9
Merge pull request #9211 from thalesmg/fix-mgmt-endpoint-status-code-v50
...
fix(mgmt_api): return 503 when emqx is not running in `/status` (5.0)
2022-10-27 11:11:00 -03:00
c157392452
docs: fix self-closing html tag, change </br> to <br/>
2022-10-27 13:57:18 +02:00
0eca531e64
feat: add `retry-after` headers to unavailable response
2022-10-25 15:01:05 -03:00
997a262c96
fix(mgmt_api): return 503 when emqx is not running in `/status` (5.0)
2022-10-24 14:53:41 -03:00
93195f7b5b
chore: fix introduced_in for new proto APIs
2022-10-24 11:53:51 +02:00
e3240b52a8
chore: bump app versions
2022-10-24 11:48:17 +02:00
508c0e84d0
Merge branch 'release-v50' into master
2022-10-24 11:46:31 +02:00
d1332b72e7
feat(api/publish): return detailed publish results
...
Prior to this change, the publish API returns 200 in most of
the cases.
This change provides more insights to the publish result.
For single message publish endpoint (`publish/`):
HTTP error codes are:
200: Everything is OK
202: No subscriber for the topic
400: When mesage is invalid message.
e.g. bad topic name or QoS out of range.
503: Failed to dispatch the message. e.g. during EMQX restart.
The response body is a JSON object with two fields
`message_id`, and `publish_result`.
The `message_id` is a globally unique ID for tracing.
`publish_result` is `"OK"` when the message is delivered
to at least one subscriber.
Otherwise `"no_subscriber"`.
`publish_result` may also be some other informative
message to hint the failure result, the content of which
may change in the future.
For `publish/bulk` endpoint:
200: When all message in the bulk are published OK
202: If at least one message in the bulk had `"no_subscriber"` result
400: When mesage is invalid message. e.g. bad topic name or
QoS out of range.
503: When there is at least one message failed at dispatch.
The reply body is a list of JSON objects having the same layout
as for hte `publish` endpoint.
2022-10-20 20:03:27 +02:00
bdaadda479
fix(banned): fix nit code
2022-10-18 13:39:48 +08:00
69701ff578
feat(banned): clean retained/delayed data when client is banned
2022-10-18 13:35:09 +08:00
c0ed8b82aa
Merge branch 'trace-log-detail-api' of https://github.com/zhongwencool/emqx into trace-log-detail-api
2022-10-17 09:49:55 +08:00
Stefan Strigler