Document that active profiles are set at build time with AOT #32543
Description
I'm not sure if this is a bug.
I am using Spring Boot 3.2.3 and GraalVM CE 21.
Here are the context in application.yaml and yaml files under resources folder.
spring:
profiles:
active: local
If I startup the service jar file with cmd "java -jar app.jar --spring.profiles.active=cluster". Activation item will be overridden and only one profile is actived. Here is the spring output log.
2024-03-21 01:01:23.325 [main][0;39m - The following 1 profile is active: "cluster"
But if I use graalvm native image to compile the service and startup AOT package with the same param, just like "./app --spring.profiles.active=cluster". Both "local" and "cluster" will be activated. Here is the spring output.
2024-03-26 15:29:23.448 [main][0;39m - The following 2 profiles are active: "cluster", "local"