Skip to content

Releases: apolloconfig/apollo

Apollo v1.4.0 Release

03 May 12:09
6b0a06a
Compare
Choose a tag to compare

This release includes several enhancements and bug fixes.

General

  • Support system environment variable APP_ID #2067
  • Support apollo-configservice/apollo-adminservice/apollo-portal run with JDK 9, 10 and 11 #2074
  • Fix k8s deployment issues #2113 #2115
  • Add TXT file format support #2181

Apollo Portal

  • Support comparing configurations among clusters #1996
  • Support updating user info when mysql has SQL_SAFE_UPDATES set to true #2016
  • Fix the bug that cannot resolve blank line in properties under Windows #2017
  • Make the duplicated key detection logic case-insensitive #2066
  • Fix SSRF issue #2105
  • Fix the gray version configuration display issue when master version has keys with empty value #2172

Apollo Open Api

  • Fix open api permission issue #1985
  • Add OpenAPI to get application information #2072

Apollo Client

  • Make apollo-core/client get more accurate host IP #1986
  • Fix the performance issue when calling getHostName #2152
  • Fix the compatibility issue with jasypt-spring-boot #2173

Installation

Please refer 分布式部署指南

How to upgrade from v1.3.0 to v1.4.0

There is no schema change between v1.3.0 and v1.4.0.
So simply deploy v1.4.0 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v1.3.0 Release

17 Feb 03:01
Compare
Choose a tag to compare

This release includes several enhancements and bug fixes.

General

  • Introduce flyway database migration tool #1828
  • Fix spec.template.spec.initContainers[1].name: Duplicate value issue when deploying with apollo-on-kubernetes #1952

Apollo Portal

  • Add import and export configs api #1767
  • Add fullscreen mode for config value editor #1788
  • Add group search support for ldap #1794
  • Optimize my-projects view to show projects which the users have admin/edit/publish permissions #1855
  • Allow empty config value #1852 #1883
  • Fix instance list pagination issue #1891
  • Do not allow user to create private app namespace with the same name as some public app namespace #1894
  • Prompt current config item that is being deleted #1898
  • Fix ldap findByUserIds error #1910
  • Add syntax check function for yaml namespace #1946
  • Add servlet initializer for apollo-portal and apollo-adminservice #1948
  • Change apollo portal port to 8070 by default #1961
  • Fix the issue that when using reverse proxy with TLS, "HttpServletResponse.sendRedirect" will redirect to http rather than https #1967
  • Limit hibernate query plan cache size #1963

Apollo Client

  • Implement Ordered for ApolloApplicationContextInitializer #1809
  • Add ConfigChangeListener with optional interested key prefixes #1871
  • Add yaml support to apollo-client #1944
  • Add rate limter for no app id warning log #1949

Apollo Admin Service

  • Fix instance list pagination issue #1891
  • Add servlet initializer for apollo-portal and apollo-adminservice #1948

Installation

Please refer 分布式部署指南

How to upgrade from v1.2.0 to v1.3.0

There is no schema change between v1.2.0 and v1.3.0.
So simply deploy v1.3.0 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v1.2.0 Release

09 Dec 06:46
dcc4983
Compare
Choose a tag to compare

This release includes several enhancements and bug fixes.

General

  • Support to override meta server url through system environment variables #1565
  • Support to config eureka.service.url via configMap for k8s #1631

Apollo Portal

  • Add active directory support for ldap #1562
  • Prevent users from deleting default cluster #1586
  • Remove nicescroll to support browser Ctrl + F function #1621
  • Allow users to create missing appnamespaces and private namespaces #1707
  • Hide namespace's body when namespace's size is bigger than 2 #1723
  • Do lazy load if page contains too many namespaces(>10) to improve page loading performance #1732 #1733
  • Add missing env and namespace alert #1734

Apollo Client

  • Provide a flag to move apollo initialization even before logging initialization #1614
  • Use weak reference to hold bean objects so that they could be garbage collected #1676

Apollo Admin Service

  • Fix gray release issue #1678

Apollo Config Service

  • Use DefaultHttpFirewall instead of StrictHttpFirewall to fix the The request was rejected because the URL was not normalized. issue when accessing meta service with extra slashes #1685

Apollo Open API

  • Add get single item interface #1704
  • Allow passing the appendNamespacePrefix flag when creating public namespaces #1704

Installation

Please refer 分布式部署指南

How to upgrade from v1.1.2 to v1.2.0

There is no schema change between v1.1.2 and v1.2.0.
So simply deploy v1.2.0 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v1.1.2 Release

01 Nov 14:04
Compare
Choose a tag to compare

This release includes the following bug fix.

General

  • Fix the 500 error when loading config via .Net client #1609

Installation

Please refer 分布式部署指南

How to upgrade from v1.1.1 to v1.1.2

There is no schema change between v1.1.1 and v1.1.2.
So simply deploy v1.1.2 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v1.1.1 Release

13 Oct 11:11
c22ac56
Compare
Choose a tag to compare

This release includes the following bug fix.

General

  • Fix the potential startup issue of chown: cannot access '': No such file or directory in centos7 #1557

Installation

Please refer 分布式部署指南

How to upgrade from v1.1.0 to v1.1.1

There is no schema change between v1.1.0 and v1.1.1.
So simply deploy v1.1.1 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v1.1.0 Release

06 Oct 13:58
7b8ccbe
Compare
Choose a tag to compare

This release includes several enhancements and bug fixes.

General

  • Add kubernetes support #1416
  • Change column 'Username' in table 'Authorities' to varchar(64) #1480
    • Yet there is no need to apply this schema change if your system is running well
  • Support rotating log files based on size and time #1494 #1495 #1530
  • Update alpine from v3.6 to v3.8 in docker files #1513
  • Rename heap_trace.txt to gc.log and make gc log rotatable #1526
  • Upgrade spring boot to 2.0.5 and spring cloud to Finchley.SR1 #1527

Apollo Portal

  • Add query function for portal server config page #1357
  • Unify portal logout url to /user/logout #1363
  • Add system info page for admin user to diagnose the system #1379
  • Add ldap support #1380
  • Fix modifing string in its iteration #1412
  • Fix content type in role assignment requests #1443
  • Allow public namespaces created with no org prefix #1476
  • Add gray release operation for Open API #1518 #1533
  • Fix the config overridden issue in server configuration page #1521
  • Optimize my-projects view to show projects which the user has admin permissions #1528
  • Support displaying configs only to team members #1531
  • Adjust cache control so that entry htmls are not cached, as we need them to trigger 302 in case user is not logged in #1535

Apollo Client

  • Add getProperty with transform function #1356
  • Check meta server real path #1415
  • Make sure ApolloBootstrapPropertySources is in the first place #1432
  • Support multiple spring contexts #1436
  • Add removeChangeListener api #1462
  • Add getSourceType api #1470
  • Fix default PropertySourcesPlaceholderConfigurer order issue #1525

Apollo Mock Server

  • Add apollo-mockserver module to support config mock in test scenarios #1397 #1403

Apollo Open API Client

  • Add apollo-openapi client to simplify open api usage for Java #1508

Installation

Please refer 分布式部署指南

How to upgrade from v1.0.0 to v1.1.0

There is no schema change between v1.0.0 and v1.1.0.
(Because it's not required to apply the schema change brought by #1480 )
So simply deploy v1.1.0 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v1.0.0 Release

09 Aug 15:35
a3cf5b2
Compare
Choose a tag to compare

This is a major release with several enhancements and bug fixes.

The biggest change with this release is apollo-client is now deployed to Maven Central Repository. Users could reference apollo-client as follows:

<dependency>
    <groupId>com.ctrip.framework.apollo</groupId>
    <artifactId>apollo-client</artifactId>
    <version>1.0.0</version>
</dependency>

General

  • Refactor meta server related logic so that apollo-core is common enough to go maven central repository. #1315
    • From 1.0.0 version, apollo-core.jar won't assemble apollo-env.properties anymore, so that we could freely deploy apollo client jars to maven central repository, which means a lot convenience for users to access apollo client jars.
    • However, for existing users, they can't upgrade apollo client jars to 1.0.0 version directly. Please check the instructions below.
  • Fix the data issue when some public app namespace is deleted and recreated in another app #1346

Apollo Client

  • Add ConfigChangeListener with optional interested keys #1328
  • Support setting apollo system properties via Spring Boot application.properties #1336

Installation

Please refer 分布式部署指南

How to upgrade Apollo servers from v0.11.0 to v1.0.0

There is no schema change between v0.11.0 and v1.0.0.
So simply deploy v1.0.0 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

How to upgrade Apollo client from v0.11.0 to v1.0.0

  1. If existing users currently pass env and ${env}_meta at runtime, they could continue to do so with no impact.
  2. If existing users currently place apollo-env.properties in their classpath, they could continue to do so with no impact.
  3. If existing users assemble meta server addresses into apollo-core.jar, then there are several solutions:
    • Create a xx-company-apollo-client jar with apollo-env.properties in classpath and depends on apollo-client. Then ask the users to depend on xx-company-apollo-client jar instead of apollo-client. This might be the most tranparent way.
    • Ask the ops to configure apollo.meta in server.properties or os env APOLLO_META
    • Ask the user to configure apollo.meta by -Dapollo.meta=http://config-service-url or app.properties manually
    • Ask the user to put the apollo-env.properties in their projects' classpath
    • For more information on how to configure meta server address, please refer 1.2.2 Apollo Meta Server

Apollo v0.11.0 Release

29 Jul 10:56
be40a4b
Compare
Choose a tag to compare

This release includes several enhancements and bug fixes.

General

  • Upgrade mysql-connector-java to 5.1.46 to support mysql 8.0 #1147
  • Support multiple meta servers for any single environment #1214
  • Simplify installation process by externalizing application-github.properties and apollo-env.properties #1273
    • apollo-portal's default server port is now changed to 8070, you may adjust it according to your actual deployment environment, see code change for more information

Apollo Client

  • Optimize Properties#stringPropertyNames performance #1072
  • When server returns status code other than 200 and 304, we should throw ApolloConfigStatusCodeException #1212
  • Make local cache dir customizable #1274 #1291
  • Support passing apollo.meta and apollo.configService via system property, etc #1275 #1291

Apollo Portal

  • Fix number display, such as 123456789789798789 #1052
  • Remove animation for default login page to make it faster #1188
  • Add delete app api #1276
  • Add delete app namespace api #1277
  • Add admin page to delete app, cluster and app namespace #1279
  • Support role permissions per environment #1282

Installation

Please refer 分布式部署指南

How to upgrade from v0.10.2 to v0.11.0

There is no schema change between v0.10.2 and v0.11.0.
So simply deploy v0.11.0 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v0.10.2 Release

30 Mar 06:23
03825fa
Compare
Choose a tag to compare

This release includes the following bug fix.

General

  • Fix init sql typo #1028

Installation

Please refer 分布式部署指南

How to upgrade from v0.9.1 to v0.10.2

There is no schema change between v0.9.1 and v0.10.2.
So simply deploy v0.10.2 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal

Apollo v0.10.1 Release

28 Mar 05:35
6b2467d
Compare
Choose a tag to compare

This release includes the following bug fix.

Apollo Client

  • Fix the issue brought by 0.10.0 that Spring related classes are mistakenly loaded via DefaultInjector #1019

How to upgrade from v0.9.1 to v0.10.1

There is no schema change between v0.9.1 and v0.10.1.
So simply deploy v0.10.1 executables with the following sequences:

  1. apollo-configservice
  2. apollo-adminservice
  3. apollo-portal