-
Notifications
You must be signed in to change notification settings - Fork 377
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Closes #9780 @TarantoolBot document Title: Expansion of `config:info()` Before this patch, the `meta` field of the `config:info()` function contained the meta data of the last load, even if it was unsuccessful reload. This can be inconvenient because if the reload fails, we expect that the last configuration that was successfully applied is used, but its metadata was lost. Now `config:info()` can take one argument — the version of the information that should be returned by the function. If no arguments are specified or the argument is the string `v1`, the return value has the same structure as before. If the argument is the string `v2`, the `meta` field in the return value has fields - `active` (meta for the last successfully applied configuration) and `last` (meta of the last loaded configuration). Currently only these values are accepted.
- Loading branch information
1 parent
5040fba
commit 699775b
Showing
3 changed files
with
271 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
## feature/config | ||
|
||
* `config:info()` can now display source metadata from the last successful | ||
load along with source metadata from the very last load attempt (gh-9780). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters