Apollo is a reliable configuration management system suitable for microservice configuration management scenarios.
Apollo now supports the H2 database, ideal for rapid deployment scenarios. For further details, refer to PR #4851.
Users can now adjust how many release histories to keep for each namespace, reducing the risk of too many histories overloading the database. For more info, please see the documentation.
The log files for Apollo ConfigService, AdminService, and Portal are now all in /opt/logs
, instead of in separate folders like /opt/logs/10003171
, /opt/logs/10003172
, and /opt/logs/10003173
.
Open API consumer tokens now include a flag indicating permission to create applications. When set to 'yes', users are enabled to create applications using the consumer token through the Open API.
Grayscale release is now enabled for non-properties namespaces, such as YAML and JSON.
Administrators now have access to detailed audit logs via the Audit Log
feature located in the Admin Tools section.
Please refer to the Distributed Deployment Guide.
User management enhancement The user management page now has a list view of all users and administrators can easily find a specific user to edit.
System configuration enhancement The system configuration page now has a list view of all configuration items of PortalDB as well as ConfigDB. Administrators can easily find a specific configuration item to edit.
Open platform authorization management enhancement The open platform authorization management page now has a list view of third-party apps and administrators can easily find a specific app to grant permission.
Users can now config the types of the item and apollo would do a basic type check based on the type. The types available now are String(default), Number, Boolean, and JSON.
The comparison feature for non-properties namespaces is now available.
Apollo now supports the use of database as the service registry, without relying on a third-party service registry such as eureka. See database-discovery for more information.
@Transactional
invalid cases by @ksice in https://github.com/apolloconfig/apollo/pull/4551
As was discussed in #4353, apollo drops the support for the flyway database migration tool.
Please refer to the Distributed Deployment Guide.
use ApolloPortalDB;
delete from `SPRING_SESSION_ATTRIBUTES`;
delete from `SPRING_SESSION`;
Please refer Distributed Deployment Guide.
There is no schema change between v2.0.0 and v2.0.1 So simply deploy v2.0.1 executables with the following sequences:
Apollo now supports Java Runtime Environment 8, 11, and 17 for both clients and servers.
A public namespaces list view is added to the apollo homepage, users could now view and search public namespaces.
Grayscale rules now support matching with labels for scenarios where IP is not fixed, e.g. Kubernetes. For more information on how to use this feature, please refer apollo user guide.
The batch config export/import feature is enhanced.
The export/import feature is also enabled for each namespace.
Previously, Apollo doesn't have unique constraint indices due to the soft delete design. However, there might be problems in concurrent situations. With the new DeletedAt
columns, unique indices are added for most of the tables. There are some manual steps for existing users to upgrade.
As was discussed in #3896, apollo-client drops java 1.7 support since the 2.0.0 release. The minimum Java runtime environment is 1.8(for both client and server).
EnvUtils
. by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4007
Env
class in apollo-portal that links to Env
enum in apollo-core by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4011
ConfigFileFormat
by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4030
ConfigFileFormat#Properties
are now fully compatible with themselves by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4033
Please refer Distributed Deployment Guide.
Important Note: 2.0.0 release adds unique indices for most of the tables by adding DeletedAt
columns, so there are some manual steps to do:
Scripts to check whether there is any duplicate data
section in PR #3866mvn -N -Pconfigdb -Dflyway.target=2.0.0 flyway:migrate
mvn -N -Pportaldb -Dflyway.target=2.0.0 flyway:migrate
mvn -N -Pconfigdb flyway:migrate
mvn -N -Pportaldb flyway:migrate
Scripts to rollback the unique indices
section in PR #3866Apollo now supports Java Runtime Environment 8, 11, and 17 for both clients and servers.
A public namespaces list view is added to the apollo homepage, users could now view and search public namespaces.
Grayscale rules now support matching with labels for scenarios where IP is not fixed, e.g. Kubernetes. For more information on how to use this feature, please refer apollo user guide.
The batch config export/import feature is enhanced.
The export/import feature is also enabled for each namespace.
Previously, Apollo doesn't have unique constraint indices due to the soft delete design. However, there might be problems in concurrent situations. With the new DeletedAt
columns, unique indices are added for most of the tables. There are some manual steps for existing users to upgrade.
As was discussed in #3896, apollo-client drops java 1.7 support since the 2.0.0 release. The minimum Java runtime environment is 1.8(for both client and server).
EnvUtils
. by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4007
Env
class in apollo-portal that links to Env
enum in apollo-core by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4011
ConfigFileFormat
by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4030
ConfigFileFormat#Properties
are now fully compatible with themselves by @DiegoKrupitza in https://github.com/apolloconfig/apollo/pull/4033
Please refer Distributed Deployment Guide.
Important Note: 2.0.0 release adds unique indices for most of the tables by adding DeletedAt
columns, so there are some manual steps to do:
Scripts to check whether there is any duplicate data
section in PR #3866mvn -N -Pconfigdb -Dflyway.target=2.0.0 flyway:migrate
mvn -N -Pportaldb -Dflyway.target=2.0.0 flyway:migrate
mvn -N -Pconfigdb flyway:migrate
mvn -N -Pportaldb flyway:migrate
Scripts to rollback the unique indices
section in PR #3866@lonre @nobodyiam
Please refer Distributed Deployment Guide
There is no schema change between v1.9.1 and v1.9.2 So simply deploy v1.9.2 executables with the following sequences:
@klboke @lijiansgit
Please refer Distributed Deployment Guide
There is no schema change between v1.9.0 and v1.9.1 So simply deploy v1.9.1 executables with the following sequences:
@vdisk-group @nobodyiam @finchcn @klboke @Loading-Life @Anilople @Technoboy- @chengasd @lonre @wilsonwu @CalebZYC @lepdou @dake0805 @Accelerater
Please refer Distributed Deployment Guide
This release includes the following fix.
Please refer Distributed Deployment Guide
There is no schema change between v1.8.1 and v1.8.2 So simply deploy v1.8.2 executables with the following sequences:
This release includes the following fix.
Please refer Distributed Deployment Guide
There is no schema change between v1.8.0 and v1.8.1 So simply deploy v1.8.1 executables with the following sequences: