Apollo Versions Save

Apollo is a reliable configuration management system suitable for microservice configuration management scenarios.

v1.8.0

3 years ago

Enhancements

  • Extend the length of AppId from 32 to 64 characters. #3228
  • Add webhook notification support for configuration releases #3235
  • Optimizing opening a namespace with lots of commits #3258
  • Add ingress support for config service and admin service #3324
  • Support resolving namespace placeholder values in annotation and xml config #3349
  • Support customizing server.properties location #3401
  • Add smtp email support #3415
  • Enhance the user experience in the scenario of submitting duplicate keys #3429
  • Add nacos service discovery support #3447
  • Switch off console appenders when running as backend services #3488
  • Upgrade spring-boot to 2.4.2 and spring-cloud to 2020.0.1 #3507
  • Add openid connect auth support for apollo-portal #3534

Bug fixes

  • Fix build.sh warning by shellcheck #3294
  • Adapt to the scenario that the ConfigService sets context-path #3320
  • Fix imagePullSecrets indent issue in helm chart #3336
  • Fix potential xss issue with user id #3340
  • Fix potential data inconsistency issue #3341
  • Fix the issue that the wrong port is used when db service is not enabled in helm chart #3385
  • Rename default git.properties to apollo.git.properties to avoid potential conflict #3390
  • Return null when EmptyResultDataAccessException occurred for ldap scenarios #3430
  • Use exec to start the java process when APOLLO_RUN_MODE is Docker #3458

Credits

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

Installation

Please refer Distributed Deployment Guide

How to upgrade from v1.7.x to v1.8.0

  1. Apply apolloconfigdb-v170-v180.sql to ApolloConfigDB
  2. Apply apolloportaldb-v170-v180.sql to ApolloPortalDB
  3. Deploy v1.8.0 executables with the following sequences:
    1. apollo-configservice
    2. apollo-adminservice
    3. apollo-portal

v1.7.2

3 years ago

This release includes the following fix.

  • update xstream to 1.4.15 #3524

Installation

Please refer 分布式部署指南

How to upgrade from v1.7.1 to v1.7.2

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

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

v1.7.1

3 years ago

This release includes the following enhancement.

  • add access control support for admin service #3233
    • thanks @lllllx for pointing out this potential security issue

Installation

Please refer 分布式部署指南

How to upgrade from v1.7.0 to v1.7.1

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

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

v1.7.0

3 years ago

Enhancements

  • Support revoking modified but unpublished configurations #2952
  • Avoid unnecessary retry for non-existing configurations in apollo-client #3056
  • Use Spring Boot native datasource variables instead of custom ones in startup script #3098
  • Show namespace comment as tooltip and item modified count in lazy init mode #3112
  • Support rollback to specified releases #3093
  • Add kubernetes native service discovery support and helm chart templates #3055 #3176 #3205
  • Change pom's static version number to ${revision} variable #3151
  • Support extracting placeholder from non-normalized expressions in apollo-client, e.g. ${user.address}/user/gateway #3178
  • Support exporting multiple configs #3088

Bug fixes

  • Add namespace permission check for import configs #2973
  • Fix a potential npe bug with BOMInputStream #3023
  • Fix a potential xss issue #3037
  • Fix a potential client authentication timestamp check issue #3029
  • Allow repeatable deletions and enhance thread safety for apollo-mockserver #3069
  • Public namespaces only allow properties format #3140

Installation

Please refer 分布式部署指南

How to upgrade from v1.6.2 to v1.7.0

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

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

v1.6.2

3 years ago

This release includes the following bug fix.

  • restrict use of custom yaml types #3175

Installation

Please refer 分布式部署指南

How to upgrade from v1.6.1 to v1.6.2

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

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

v1.6.1

4 years ago

This release includes the following bug fix.

  • fix the issue that authorities record will be deleted mistakenly #2977

Installation

Please refer 分布式部署指南

How to upgrade from v1.6.0 to v1.6.1

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

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

v1.6.0

4 years ago

Enhancements

  • Support last modified by display for deleted item #2680
  • Support case-insensitive appid for change notification and gray release rule #2696 #2928
  • Support sorting items by publish status #2705
  • Support using relative path to access portal via reverse proxy or slb #2754 #2807 #2929
  • Add access key mechanism so that sensitive configurations can only be retrieved for authenticated clients #2828 #2883 #2888
  • Add ordered properties feature so that user could choose to keep the configuration order as is displayed in apollo portal #2861 #2912
  • Support adding customized environments without any code change #2867 #2930 #2953 #2958

Bug fixes

  • Fix the issue that the namespace length is mis-calculated for private namespaces and public namespaces which don't need to append prefix #2784
  • Fix the issue that app search path is conflicted with app named 'search' #2805
  • Fix potential NPE issue when ReleaseComment is null. #2814
  • Fix the issue that openapi item comment could be too long #2849
  • Fix the associated namespace's unreleased configuration table header dislocation issue #2914
  • Fix the issue that findByUserId in ldap always return the first user #2915

Installation

Please refer 分布式部署指南

How to upgrade from v1.5.1 to v1.6.0

  1. Apply apolloconfigdb-v151-v160.sql to ApolloConfigDB
  2. Deploy v1.6.0 executables with the following sequences:
  • apollo-configservice
  • apollo-adminservice
  • apollo-portal

v1.5.1

4 years ago

This release includes the following bug fixes.

  • fix AppId displayed as Department issue #2726
  • fix miscellaneous bugs and polish code #2678

Installation

Please refer 分布式部署指南

How to upgrade from v1.5.0 to v1.5.1

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

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

v1.5.0

4 years ago

This release includes several enhancements and bug fixes.

General

  • Startup scripts support setting server port, datasource and meta server information via environment variables, so that one Docker image could run in different environments #2333 #2343 #2628
  • Use podAntiAffinity instead of nodeSelector for k8s deployments to deploy services in different nodes #2398
  • Add mvn wrapper #2442
  • Add prometheus integration, expose process information via /prometheus and /metrics #2507 #2633 #2638
  • Simplify health check logic #2642

Apollo Portal

  • Fix the issue that a non-properties namespace could not be cleared #2320
  • Search app from backend instead of loading all app and filter in frontend #2321
  • Fix ldap userId incorrect case issue #2326
  • Add create-application and manange and manage-app-master permissions #2309 #2627 #2629
  • Fix potential permission issue #2496
  • Fix input validator for app namespace name #2634
  • Fix delete grayscale item cluster mismatch issue #2639
  • Add i18n support and English translations #2452 #2641 #2675
  • Fix delete children clusters twice issue #2645
  • Auto append build time as version for js and css files to invalidate static file cache for new versions #2674

Apollo Config Service

  • Fix the potential concurrency issue in NotificationControllerV2 #2255
  • Add options to disable apollo-configservice started as eureka server #2478
  • Support configuring server side's long polling timeout #2532 #2543 #2630

Apollo Open Api

  • Fix the gson dateformat issue #2462
  • Add cluster related and rollback release open api #2581 #2590 #2631 #2636

Apollo Client

  • Fix the occasional NullPointerException issue in SpringValueRegistry #2281
  • Support setting apollo.cacheDir from app.properties #2317
  • Support ordering for spring processors #2313
  • Optimize app.id loading logic #2515
  • Fix ConfigFileChangeListener removal api #2623
  • Fix setting null value of property in xml throws NullPointerException #2646 #2677

Installation

Please refer 分布式部署指南

How to upgrade from v1.4.0 to v1.5.0

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

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

v1.4.0

5 years ago

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