Apollo is a reliable configuration management system suitable for microservice configuration management scenarios.
Thanks for everyone who contributed to this release!
@Anilople @Ayden-Franklin @changfubai @CoolDarran @HuangSheng @JaredTan95 @jiangcaijun @kezhenxu94 @klboke @nisiyong @nobodyiam @Q-RK @vdisk-group @waters00 @WisWang @xiagw @ywf4026
Please refer Distributed Deployment Guide
This release includes the following fix.
Please refer 分布式部署指南
There is no schema change between v1.7.1 and v1.7.2 So simply deploy v1.7.2 executables with the following sequences:
This release includes the following enhancement.
Please refer 分布式部署指南
There is no schema change between v1.7.0 and v1.7.1 So simply deploy v1.7.1 executables with the following sequences:
Please refer 分布式部署指南
There is no schema change between v1.6.2 and v1.7.0 So simply deploy v1.7.0 executables with the following sequences:
This release includes the following bug fix.
Please refer 分布式部署指南
There is no schema change between v1.6.1 and v1.6.2 So simply deploy v1.6.2 executables with the following sequences:
This release includes the following bug fix.
Please refer 分布式部署指南
There is no schema change between v1.6.0 and v1.6.1. So simply deploy v1.6.1 executables with the following sequences:
Please refer 分布式部署指南
This release includes the following bug fixes.
AppId
displayed as Department
issue #2726Please refer 分布式部署指南
There is no schema change between v1.5.0 and v1.5.1. So simply deploy v1.5.1 executables with the following sequences:
This release includes several enhancements and bug fixes.
/prometheus
and /metrics
#2507 #2633 #2638Please refer 分布式部署指南
There is no schema change between v1.4.0 and v1.5.0. So simply deploy v1.5.0 executables with the following sequences:
This release includes several enhancements and bug fixes.
APP_ID
#2067SQL_SAFE_UPDATES
set to true #2016Please refer 分布式部署指南
There is no schema change between v1.3.0 and v1.4.0. So simply deploy v1.4.0 executables with the following sequences: