Hello Igniters, I would like to present two pull requests [1], [2] with basic implementation of IEP-55 for Unified Configuration [3] and IEP-63 REST API for Unified Configuration [4].
The main goal of these PRs is to present and discuss a new approach for preparing and managing Ignite configuration in a more robust and convenient way than it was before. These PRs cover basic aspects of configuration but other steps for developing functionality are already defined; ticket IGNITE-13511 [5] summarizes work to do. In a nutshell proposed approach to configuration is as follows: We want to declare configuration with POJO-based schemas that are concise and contain all important information about validation and how different pieces of configuration relate to each other. When schemas are marked with annotations annotation processor enters the game and generates most of boilerplate code thus freeing users from writing it by hand. REST API module from [2] contains an example of managing configuration and exposing it to external tools like a Unified CLI tool presented in [6]. [1] https://github.com/apache/ignite-3/pull/5 [2] https://github.com/apache/ignite-3/pull/6 [3] https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration [4] https://cwiki.apache.org/confluence/display/IGNITE/IEP-63%3A+REST+API+module+to+integrate+new+modular+architecture+and+management [5] https://issues.apache.org/jira/browse/IGNITE-13511 [6] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Unified-CLI-tool-td50618.html
