yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chore: missing change log for duplicated apikey fixing

This commit is contained in:
JimMoen 2023-10-24 09:43:08 +08:00
parent a9b42af8b3
commit 99fab8dc5d
No known key found for this signature in database
GPG Key ID: 87A520B4F76BA86D
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
apps/emqx_management/src/emqx_mgmt_auth.erl
View File

@ -262,7 +262,9 @@ maybe_cleanup_api_key(#?APP{name = Name, api_key = ApiKey}) ->
[_App1] -> [_App1] ->
?SLOG(info, #{ ?SLOG(info, #{
msg => "update_apikey_name_from_old_version", msg => "update_apikey_name_from_old_version",
info => <<"Update ApiKey name with new name rule, more information: xxx">> info =>
<<"Update ApiKey name with new name rule, see also: ",
"https://github.com/emqx/emqx/pull/11798">>
}), }),
ok; ok;
Existed -> Existed ->

5
changes/ce/fix-11798.en.md Normal file
View File

@ -0,0 +1,5 @@
Fixed the issue where the node could not start after executing `./bin/emqx data import [FILE]`.
And strongly bind apikey's `apikey_key` to `apikey_name`.
- `apikey_key` will generate a unique value from the given human-readable `apikey_name` when generating an apikey using dashboard.
- `apikey_name` will be a unique value generated by `apikey_key` when using bootstrap file to generate apikey, .