Repository navigation
Default new installs to database discovery - #5580
Merged
nobodyiam merged 3 commits intoMar 21, 2026
Merged
Conversation
dosubot
Bot
added
the
size:M
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR makes database-discovery enabled by default for apollo-configservice and apollo-adminservice in official builds: build scripts now include the Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (4)
docs/en/deployment/distributed-deployment-guide.md (4)
516-517: Clarify thateureka.service.urlonly applies to Eureka deployments.Since database-discovery is now the default, the reference to updating
eureka.service.urlat the end of this note might confuse users. Consider making it explicit that this part only applies when using Eureka.✏️ Suggested clarification
-> Note 3: To adjust the listening port of the service, you can modify the `SERVER_PORT` in scripts/startup.sh. In addition, apollo-configservice also assumes the responsibility of meta server. If you want to modify the port, update the meta server information used by apollo-portal and apollo-client as well. For details, see [2.2.1.1.2.4 Configuring the meta service information of apollo-portal](en/deployment/distributed-deployment-guide?id=_221124-configuring-apollo-portal39s-meta-service-information) and [1.2.2 Apollo Meta Server](en/client/java-sdk-user-guide?id=_122-apollo-meta-server). If you still use the built-in Eureka, you also need to update the `eureka.service.url` configuration item in the ApolloConfigDB.ServerConfig table. +> Note 3: To adjust the listening port of the service, you can modify the `SERVER_PORT` in scripts/startup.sh. In addition, apollo-configservice also assumes the responsibility of meta server. If you want to modify the port, update the meta server information used by apollo-portal and apollo-client as well. For details, see [2.2.1.1.2.4 Configuring the meta service information of apollo-portal](en/deployment/distributed-deployment-guide?id=_221124-configuring-apollo-portal39s-meta-service-information) and [1.2.2 Apollo Meta Server](en/client/java-sdk-user-guide?id=_122-apollo-meta-server). +> +> If you still use the built-in Eureka (instead of database-discovery), you also need to update the `eureka.service.url` configuration item in the ApolloConfigDB.ServerConfig table.Note: This change also addresses the markdownlint warning (MD028) by properly separating the Eureka-specific guidance. Based on the static analysis hint about blank lines in blockquotes.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/en/deployment/distributed-deployment-guide.md` around lines 516 - 517, Update the note in distributed-deployment-guide.md to explicitly state that the `eureka.service.url` change only applies when running with Eureka (not the default database-discovery); mention that `SERVER_PORT` can be changed in scripts/startup.sh and that apollo-configservice acts as meta server so apollo-portal and apollo-client must update their meta info, then add a separate sentence or paragraph for Eureka-specific guidance referencing the `eureka.service.url` configuration in the ApolloConfigDB.ServerConfig table to avoid confusion and to satisfy MD028 by separating the Eureka note from the general port/meta guidance.
480-481: Consider breaking this long note into shorter sentences.This note covers three important concepts in one sentence: (1) default profiles for new builds, (2) rollback for existing Eureka deployments, and (3) different methods based on deployment type. Breaking it into 2-3 shorter sentences would improve readability.
📝 Suggested restructuring
-> Note: When built with the official `build.sh/build.bat` script, `apollo-configservice` and `apollo-adminservice` default to `github,database-discovery`, while `apollo-portal` defaults to `github,auth`. If you are rebuilding source for an existing Eureka deployment and want to keep the old behavior, change the corresponding Maven command back to `-Dapollo_profile=github`. For already unpacked installation packages or running containers, explicitly set `SPRING_PROFILES_ACTIVE=github`, or configure `spring.profiles.active=github` in `config/application.properties`. +> Note: When built with the official `build.sh/build.bat` script, `apollo-configservice` and `apollo-adminservice` default to `github,database-discovery`, while `apollo-portal` defaults to `github,auth`. +> +> If you are rebuilding source for an existing Eureka deployment and want to keep the old behavior, change the corresponding Maven command back to `-Dapollo_profile=github`. +> +> For already unpacked installation packages or running containers, explicitly set `SPRING_PROFILES_ACTIVE=github`, or configure `spring.profiles.active=github` in `config/application.properties`.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/en/deployment/distributed-deployment-guide.md` around lines 480 - 481, Split the long Note into 2–3 shorter sentences: first state the default profiles for freshly built services (apollo-configservice and apollo-adminservice → github,database-discovery; apollo-portal → github,auth), then add a separate sentence explaining how to preserve the old behavior when rebuilding source (use the Maven flag -Dapollo_profile=github), and finally a short sentence covering already unpacked packages or containers and the two ways to set the profile (environment variable SPRING_PROFILES_ACTIVE=github or set spring.profiles.active=github in config/application.properties). Keep each sentence focused and use the exact identifiers (build.sh/build.bat, -Dapollo_profile=github, SPRING_PROFILES_ACTIVE, config/application.properties, apollo-configservice, apollo-adminservice, apollo-portal).
500-501: Consider breaking this long note into shorter sentences.Similar to the note at line 480, this combines multiple concepts in one sentence. Breaking it into separate sentences would improve readability and make the rollback instructions easier to follow.
📝 Suggested restructuring
-> Note: Installation packages for `apollo-configservice` and `apollo-adminservice` generated from the official release packages, Docker images, or `build.sh/build.bat` now enable `database-discovery` by default. If you want an upgraded legacy Eureka deployment to keep the old behavior, explicitly set `SPRING_PROFILES_ACTIVE=github` at runtime, or configure `spring.profiles.active=github` in the unpacked `config/application.properties`. +> Note: Installation packages for `apollo-configservice` and `apollo-adminservice` generated from the official release packages, Docker images, or `build.sh/build.bat` now enable `database-discovery` by default. +> +> If you want an upgraded legacy Eureka deployment to keep the old behavior, explicitly set `SPRING_PROFILES_ACTIVE=github` at runtime, or configure `spring.profiles.active=github` in the unpacked `config/application.properties`.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/en/deployment/distributed-deployment-guide.md` around lines 500 - 501, Split the long note starting with "Note: Installation packages for `apollo-configservice`..." into shorter sentences for clarity: state first that new installation packages and images now enable `database-discovery` by default for `apollo-configservice` and `apollo-adminservice`, then provide a separate sentence explaining how to retain legacy Eureka behavior by setting `SPRING_PROFILES_ACTIVE=github` at runtime or `spring.profiles.active=github` in the unpacked `config/application.properties`; ensure the `database-discovery`, `SPRING_PROFILES_ACTIVE`, `spring.profiles.active`, `config/application.properties`, `apollo-configservice`, and `apollo-adminservice` tokens are preserved so readers can locate the exact settings.
756-759: Minor terminology inconsistency.Lines 757-759 use different phrasing for the rollback scenarios compared to the notes at lines 480-481 and 500-501. While not incorrect, using consistent terminology would improve the documentation quality.
🔄 Suggested consistency improvement
For better consistency with earlier notes, consider aligning the terminology:
2. If you are upgrading an existing Eureka deployment and want to keep the old behavior, choose the rollback method based on how you deploy: - - Unpacked installation packages or containers at runtime: set `SPRING_PROFILES_ACTIVE=github`, or configure `spring.profiles.active=github` in `config/application.properties` + - Unpacked installation packages or running containers: explicitly set `SPRING_PROFILES_ACTIVE=github` at runtime, or configure `spring.profiles.active=github` in `config/application.properties` - Source rebuilds: change the build command from `-Dapollo_profile=github,database-discovery` back to `-Dapollo_profile=github`This matches the phrasing used in the notes at lines 480 and 500.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/en/deployment/distributed-deployment-guide.md` around lines 756 - 759, The two rollback bullets use phrasing that differs from earlier notes; update the wording to match the terminology and structure used previously by referring to the same deployment categories and option names (use SPRING_PROFILES_ACTIVE / spring.profiles.active for unpacked packages/containers and the -Dapollo_profile build flags for source rebuilds), e.g., rephrase the introductory sentence and each bullet so they mirror the earlier notes' wording and order while keeping the exact symbols SPRING_PROFILES_ACTIVE, spring.profiles.active, -Dapollo_profile=github,database-discovery and -Dapollo_profile=github for clarity.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/zh/deployment/distributed-deployment-guide.md`:
- Around line 498-500: Remove the stray blank line separating the two blockquote
lines so the two notes remain a contiguous blockquote; locate the lines starting
with "> 注3：" and "> 注4：" in the distributed-deployment-guide.md content and
delete the empty line between them so the blockquote sequence is uninterrupted.
In `@scripts/build.sh`:
- Line 45: The mvn invocation in scripts/build.sh expands unquoted datasource
vars which can break the shell when values contain special characters (e.g. &);
update the mvn command that builds apollo-configservice and apollo-adminservice
to wrap the three datasource -D args in quotes (e.g.
-Dspring_datasource_url="$apollo_config_db_url",
-Dspring_datasource_username="$apollo_config_db_username",
-Dspring_datasource_password="$apollo_config_db_password") so variable expansion
is safe; keep the rest of the mvn options unchanged.
---
Nitpick comments:
In `@docs/en/deployment/distributed-deployment-guide.md`:
- Around line 516-517: Update the note in distributed-deployment-guide.md to
explicitly state that the `eureka.service.url` change only applies when running
with Eureka (not the default database-discovery); mention that `SERVER_PORT` can
be changed in scripts/startup.sh and that apollo-configservice acts as meta
server so apollo-portal and apollo-client must update their meta info, then add
a separate sentence or paragraph for Eureka-specific guidance referencing the
`eureka.service.url` configuration in the ApolloConfigDB.ServerConfig table to
avoid confusion and to satisfy MD028 by separating the Eureka note from the
general port/meta guidance.
- Around line 480-481: Split the long Note into 2–3 shorter sentences: first
state the default profiles for freshly built services (apollo-configservice and
apollo-adminservice → github,database-discovery; apollo-portal → github,auth),
then add a separate sentence explaining how to preserve the old behavior when
rebuilding source (use the Maven flag -Dapollo_profile=github), and finally a
short sentence covering already unpacked packages or containers and the two ways
to set the profile (environment variable SPRING_PROFILES_ACTIVE=github or set
spring.profiles.active=github in config/application.properties). Keep each
sentence focused and use the exact identifiers (build.sh/build.bat,
-Dapollo_profile=github, SPRING_PROFILES_ACTIVE, config/application.properties,
apollo-configservice, apollo-adminservice, apollo-portal).
- Around line 500-501: Split the long note starting with "Note: Installation
packages for `apollo-configservice`..." into shorter sentences for clarity:
state first that new installation packages and images now enable
`database-discovery` by default for `apollo-configservice` and
`apollo-adminservice`, then provide a separate sentence explaining how to retain
legacy Eureka behavior by setting `SPRING_PROFILES_ACTIVE=github` at runtime or
`spring.profiles.active=github` in the unpacked `config/application.properties`;
ensure the `database-discovery`, `SPRING_PROFILES_ACTIVE`,
`spring.profiles.active`, `config/application.properties`,
`apollo-configservice`, and `apollo-adminservice` tokens are preserved so
readers can locate the exact settings.
- Around line 756-759: The two rollback bullets use phrasing that differs from
earlier notes; update the wording to match the terminology and structure used
previously by referring to the same deployment categories and option names (use
SPRING_PROFILES_ACTIVE / spring.profiles.active for unpacked packages/containers
and the -Dapollo_profile build flags for source rebuilds), e.g., rephrase the
introductory sentence and each bullet so they mirror the earlier notes' wording
and order while keeping the exact symbols SPRING_PROFILES_ACTIVE,
spring.profiles.active, -Dapollo_profile=github,database-discovery and
-Dapollo_profile=github for clarity.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e5f9df58-c28e-4a61-9ab8-500368d32cf7
📒 Files selected for processing (9)
CHANGES.mdapollo-adminservice/src/main/docker/Dockerfileapollo-adminservice/src/main/resources/application.propertiesapollo-configservice/src/main/docker/Dockerfileapollo-configservice/src/main/resources/application.propertiesdocs/en/deployment/distributed-deployment-guide.mddocs/zh/deployment/distributed-deployment-guide.mdscripts/build.batscripts/build.sh
Comment on lines
+498
to
+500
| > 注3：如要调整服务的监听端口，可以修改scripts/startup.sh中的`SERVER_PORT`。另外apollo-configservice同时承担meta server职责，如果要修改端口，需要同步更新apollo-portal和apollo-client中的meta server信息，详见：[2.2.1.1.2.4 配置apollo-portal的meta service信息](#_221124-配置apollo-portal的meta-service信息)和[1.2.2 Apollo Meta Server](zh/client/java-sdk-user-guide#_122-apollo-meta-server)。如果当前仍使用内置Eureka，还需要同时更新ApolloConfigDB.ServerConfig表中的`eureka.service.url`配置项。 | ||
|
|
||
| > 注4：如果ApolloConfigDB.ServerConfig的eureka.service.url只配了当前正在启动的机器的话，在启动apollo-configservice的过程中会在日志中输出eureka注册失败的信息，如`com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused`。需要注意的是，这个是预期的情况，因为apollo-configservice需要向Meta Server（它自己）注册服务，但是因为在启动过程中，自己还没起来，所以会报这个错。后面会进行重试的动作，所以等自己服务起来后就会注册正常了。 | ||
| > 注4：仅当继续使用内置Eureka时，如果ApolloConfigDB.ServerConfig的`eureka.service.url`只配了当前正在启动的机器，那么在启动apollo-configservice的过程中会在日志中输出eureka注册失败的信息，如`com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused`。这是预期现象，因为apollo-configservice需要向Meta Server（它自己）注册服务，但在启动过程中自己还没有完全起来。后续会自动重试，等服务启动完成后注册就会正常。 |
Contributor
There was a problem hiding this comment.
Remove the blank line inside this blockquote sequence.
There is a blank line between > 注3 and > 注4, which can trigger markdown lint/render inconsistencies. Keep the blockquote lines contiguous.
✏️ Suggested markdown fix
> 注3：如要调整服务的监听端口，可以修改scripts/startup.sh中的`SERVER_PORT`。另外apollo-configservice同时承担meta server职责，如果要修改端口，需要同步更新apollo-portal和apollo-client中的meta server信息，详见：[2.2.1.1.2.4 配置apollo-portal的meta service信息](`#_221124-配置apollo-portal的meta-service信息`)和[1.2.2 Apollo Meta Server](zh/client/java-sdk-user-guide#_122-apollo-meta-server)。如果当前仍使用内置Eureka，还需要同时更新ApolloConfigDB.ServerConfig表中的`eureka.service.url`配置项。
-
> 注4：仅当继续使用内置Eureka时，如果ApolloConfigDB.ServerConfig的`eureka.service.url`只配了当前正在启动的机器，那么在启动apollo-configservice的过程中会在日志中输出eureka注册失败的信息，如`com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused`。这是预期现象，因为apollo-configservice需要向Meta Server（它自己）注册服务，但在启动过程中自己还没有完全起来。后续会自动重试，等服务启动完成后注册就会正常。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| > 注3：如要调整服务的监听端口，可以修改scripts/startup.sh中的`SERVER_PORT`。另外apollo-configservice同时承担meta server职责，如果要修改端口，需要同步更新apollo-portal和apollo-client中的meta server信息，详见：[2.2.1.1.2.4 配置apollo-portal的meta service信息](#_221124-配置apollo-portal的meta-service信息)和[1.2.2 Apollo Meta Server](zh/client/java-sdk-user-guide#_122-apollo-meta-server)。如果当前仍使用内置Eureka，还需要同时更新ApolloConfigDB.ServerConfig表中的`eureka.service.url`配置项。 | |
| > 注4：如果ApolloConfigDB.ServerConfig的eureka.service.url只配了当前正在启动的机器的话，在启动apollo-configservice的过程中会在日志中输出eureka注册失败的信息，如`com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused`。需要注意的是，这个是预期的情况，因为apollo-configservice需要向Meta Server（它自己）注册服务，但是因为在启动过程中，自己还没起来，所以会报这个错。后面会进行重试的动作，所以等自己服务起来后就会注册正常了。 | |
| > 注4：仅当继续使用内置Eureka时，如果ApolloConfigDB.ServerConfig的`eureka.service.url`只配了当前正在启动的机器，那么在启动apollo-configservice的过程中会在日志中输出eureka注册失败的信息，如`com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused`。这是预期现象，因为apollo-configservice需要向Meta Server（它自己）注册服务，但在启动过程中自己还没有完全起来。后续会自动重试，等服务启动完成后注册就会正常。 | |
| > 注3：如要调整服务的监听端口，可以修改scripts/startup.sh中的`SERVER_PORT`。另外apollo-configservice同时承担meta server职责，如果要修改端口，需要同步更新apollo-portal和apollo-client中的meta server信息，详见：[2.2.1.1.2.4 配置apollo-portal的meta service信息](`#_221124-配置apollo-portal的meta-service信息`)和[1.2.2 Apollo Meta Server](zh/client/java-sdk-user-guide#_122-apollo-meta-server)。如果当前仍使用内置Eureka，还需要同时更新ApolloConfigDB.ServerConfig表中的`eureka.service.url`配置项。 | |
| > 注4：仅当继续使用内置Eureka时，如果ApolloConfigDB.ServerConfig的`eureka.service.url`只配了当前正在启动的机器，那么在启动apollo-configservice的过程中会在日志中输出eureka注册失败的信息，如`com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused`。这是预期现象，因为apollo-configservice需要向Meta Server（它自己）注册服务，但在启动过程中自己还没有完全起来。后续会自动重试，等服务启动完成后注册就会正常。 |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 498-498: Link fragments should be valid
(MD051, link-fragments)
[warning] 499-499: Blank line inside blockquote
(MD028, no-blanks-blockquote)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/zh/deployment/distributed-deployment-guide.md` around lines 498 - 500,
Remove the stray blank line separating the two blockquote lines so the two notes
remain a contiguous blockquote; locate the lines starting with "> 注3：" and ">
注4：" in the distributed-deployment-guide.md content and delete the empty line
between them so the blockquote sequence is uninterrupted.
| echo "==== starting to build config-service and admin-service ====" | ||
|
|
||
| mvn clean package -DskipTests -pl apollo-configservice,apollo-adminservice -am -Dapollo_profile=github -Dspring_datasource_url=$apollo_config_db_url -Dspring_datasource_username=$apollo_config_db_username -Dspring_datasource_password=$apollo_config_db_password | ||
| mvn clean package -DskipTests -pl apollo-configservice,apollo-adminservice -am -Dapollo_profile=github,database-discovery -Dspring_datasource_url=$apollo_config_db_url -Dspring_datasource_username=$apollo_config_db_username -Dspring_datasource_password=$apollo_config_db_password |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify unquoted datasource -D arguments in shell build scripts.
rg -nP --type=sh 'mvn .* -Dspring_datasource_(url|username|password)=\$[A-Za-z_][A-Za-z0-9_]*' scripts/build.shRepository: apolloconfig/apollo
Length of output: 606
Quote datasource -D arguments to avoid shell parsing breaks.
The unquoted datasource variable expansions can cause command failures if values contain special characters like &. JDBC URLs commonly include & in query parameters, making this a real risk.
Proposed fix
-mvn clean package -DskipTests -pl apollo-configservice,apollo-adminservice -am -Dapollo_profile=github,database-discovery -Dspring_datasource_url=$apollo_config_db_url -Dspring_datasource_username=$apollo_config_db_username -Dspring_datasource_password=$apollo_config_db_password
+mvn clean package -DskipTests -pl apollo-configservice,apollo-adminservice -am -Dapollo_profile=github,database-discovery "-Dspring_datasource_url=$apollo_config_db_url" "-Dspring_datasource_username=$apollo_config_db_username" "-Dspring_datasource_password=$apollo_config_db_password"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@scripts/build.sh` at line 45, The mvn invocation in scripts/build.sh expands
unquoted datasource vars which can break the shell when values contain special
characters (e.g. &); update the mvn command that builds apollo-configservice and
apollo-adminservice to wrap the three datasource -D args in quotes (e.g.
-Dspring_datasource_url="$apollo_config_db_url",
-Dspring_datasource_username="$apollo_config_db_username",
-Dspring_datasource_password="$apollo_config_db_password") so variable expansion
is safe; keep the rest of the mvn options unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's the purpose of this PR
Switch the official open source Config/Admin packaging defaults from built-in Eureka to
database-discoveryfor new installations, while preserving Eureka as an explicit compatibility fallback for upgraded deployments.This change intentionally does not refactor runtime discovery selection. It only changes the official packaging/install defaults and updates the deployment docs so that:
github,database-discoverySPRING_PROFILES_ACTIVE=github,spring.profiles.active=github, or rebuilding with-Dapollo_profile=githubWhich issue(s) this PR fixes:
N/A
Brief changelog
scripts/build.shandscripts/build.batso Config/Admin packages default togithub,database-discoverygithub,authdatabase-discoveryas supported since 2.1.0 and default since 3.0.0CHANGES.mdwith an explicit release-note entry for this default behavior change and the Eureka fallback pathFollow this checklist to help us incorporate your contribution quickly and easily:
mvn clean testto make sure this pull request doesn't break anything.mvn spotless:applyto format your code.CHANGESlog.Verification details
./mvnw spotless:apply./mvnw clean test./mvnw -DskipTests package -pl apollo-configservice,apollo-adminservice -am -Dapollo_profile=github,database-discovery '-Dspring_datasource_url=jdbc:mysql://127.0.0.1:3306/ApolloConfigDB?characterEncoding=utf8' -Dspring_datasource_username=apollo -Dspring_datasource_password=apolloapplication.ymldefaults togithub,database-discoverySPRING_PROFILES_ACTIVE=githubstill activates the legacy Eureka profile pathSummary by CodeRabbit
New Features
Documentation
Chores