let use can change spring.profiles.active's value without rebuild the project

[Anilople]

in https://github.com/apolloconfig/apollo/blob/67030ba4867d34b25d5fdc5b6c02a65b6c7d759c/apollo-configservice/src/main/resources/application.yml

spring:
  application:
    name: apollo-configservice
  profiles:
    active: ${apollo_profile}

${apollo_profile} will be resolved when build the project.

Could we let use can change spring.profiles.active's value without rebuild the project?

When user want to use consul-discovery, zookeeper-discovery or custom-defined-discovery, they only need to change the config instead of rebuild the project again.

[nobodyiam]

I think there are several ways to achieve this, e.g.

1. ENV - take the helm chart as an example. I suppose users could also set the env in the startup conf files.
2. System Properties - take the startup.sh as an example

[Anilople]

How about add a new file config/application.properties in .zip with default config

spring.profiles.active = github

when user want to use zookeeper, change it to

spring.profiles.active = github,zookeeper-discovery

And delete spring.profiles.active in application.yml in .jar file.

This way will be better?

[nobodyiam]

There is already an application.properties, so we need to use another file name, e.g. application.yaml.
However, I don't think it's a common use case to change the spring profiles, but we may place an application.yaml file in the config folder, filled with some commented sample configs and documentation.

# You may uncomment the following config to activate different spring profiles
#spring:
#  profiles:
#    active: github,some-customer-profile

Then we could also update the distributed deployment document to let the user customize other configs in the application.yaml instead of the application-github.properties.