config: set config status after "post_apply" phase
Previously, the config status was set after the "apply" phase, and then set again after the "post_apply" phase. This can lead to a situation where the status becomes "ready" after the "apply" phase and changes to "check_errors" or "check_warnings" after the "post_apply" phase. Because of this, it was possible that config:reload() may be called from a role or an app even if though the config loading is not finished. Note that due to this change, the "startup_in_progress" and "reload_in_progress" statuses are now expanded to include the "post_apply" phase. Also note that the status still changes before the "extras.post_apply" stage. Needed for https://github.com/tarantool/tarantool-ee/issues/643 NO_DOC=internal
Showing
- changelogs/unreleased/ghe-643-set-status-after-post-apply.md 3 additions, 0 deletionschangelogs/unreleased/ghe-643-set-status-after-post-apply.md
- src/box/lua/config/init.lua 0 additions, 2 deletionssrc/box/lua/config/init.lua
- test/config-luatest/app_test.lua 1 addition, 1 deletiontest/config-luatest/app_test.lua
- test/config-luatest/config_test.lua 42 additions, 2 deletionstest/config-luatest/config_test.lua
- test/config-luatest/roles_test.lua 5 additions, 2 deletionstest/config-luatest/roles_test.lua
Loading
Please register or sign in to comment