1.0.1(Jun 12, 2019)
This version contains several optimizations and bug fixes, and also some important features.
Extended health checker are now supported #359. Thanks to the contribution of @XCXCXCXCX, you can follow the README to build your own health checkers.
We also introduce a new interface NamingMaintainService
in #747, which contains methods to update instances and edit services. Thanks to @chuntaojun.
Hostname can now be registered in Nacos, the related issue is #963. Thanks to @Albert-Hugo.
The complete list of issues is:
- [#359] Support user extended health check type
- [#747] Add create and update service methods in SDK
- [#827] Nacos Naming's log settings affect the root log
- [#876] Nacos web management console cannot display cluster node status
- [#963] Does nacos support to register a instance with host name?
- [#1003] Nacos configuration list fuzzy query is invalid
- [#1007] "enabled" and "enable" are Inconsistent
- [#1062] Selector should not select the disable instance
- [#1069] Client beat failed if beat info is too large
- [#1075] NamingEvent add getGroupName and getClusters method
- [#1084] The console adds yaml validator
- [#1091] Healthy server list inconsistent in some situations
- [#1118] Historical profile retention time changed from 30 days to configurable
- [#1148] Windows script cannot specify FUNCTION_MODE
- [#1150] Correct the Relationship between Services and Clusters
- [#1154] [Feature] Nacos Client supports the update of service instances' metadata
- [#1215] Nacos heartbeat log is too frequent once a second, it is recommended to change to debug level
- [#1217] cannot deploy nacos server inside EDAS
- [#1227] DomainsManagerTest and RaftStoreTest Don't Work
- [#1306] Nacos Client Support Multi Enviroment Switch
- [#1308] the judgement that whether server contains ":" should judge every server,not the first one
- [#1319] Can Nacos support query instances using keyword?
- [#1334] Always failed when update instance healthy status