So with the change in how versioning works. A change to how config is loaded by default and a split between cloud agnostic spring-cloud and vendor specific integration types. There has been a major shake up on how to upgrade to the next minor version of spring-boot.
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
- <version>2.2.11.RELEASE</version>
+ <version>2.4.4</version>
<relativePath></relativePath><!--empty to not look up parent folder which is a helper pom on building-->
</parent>
-<spring-cloud.version>Hoxton.SR5</spring-cloud.version> <!-- https://spring.io/projects/spring-cloud release trains, Greenwich 2.1.x, Haxton 2.2.x -->
+<spring-cloud.version>2020.0.2</spring-cloud.version> <!-- https://spring.io/projects/spring-cloud release trains, Greenwich 2.1.x, Haxton 2.2.x, 2020.0.2 2.4.x -->
We now need to include io.awspring.cloud:spring-cloud-aws-dependencies as its now not included in the upstream org.springframework.cloud:spring-cloud-dependencies
<dependencyManagement>
<dependencies>
<!-- spring cloud and aws cloud for param store lookup -->
<dependency><scope>import</scope><groupId>org.springframework.cloud</groupId><artifactId>spring-cloud-dependencies</artifactId><version>${spring-cloud.version}</version><type>pom</type></dependency>
+ <dependency><scope>import</scope><groupId>io.awspring.cloud</groupId><artifactId>spring-cloud-aws-dependencies</artifactId><version>2.3.1</version><type>pom</type></dependency>
..
With dependencies we don't include spring-cloud-starter any more but with bootstrap.yml not being the 'default' way for loading we now need to include spring-cloud-starter-bootstrap to re-enable that functionality
- <dependency><groupId>org.springframework.cloud</groupId><artifactId>spring-cloud-starter</artifactId></dependency>
- <dependency><groupId>org.springframework.cloud</groupId><artifactId>spring-cloud-starter-aws-parameter-store-config</artifactId></dependency>
+ <!-- spring-cloud-starter-bootstrap required to enable bootstrap.yml due to it not being default anymore -->
+ <dependency><groupId>org.springframework.cloud</groupId><artifactId>spring-cloud-starter-bootstrap</artifactId></dependency>
+ <!-- aws parm store config changed home-->
+ <dependency><groupId>io.awspring.cloud</groupId><artifactId>spring-cloud-starter-aws-parameter-store-config</artifactId></dependency>
You now can't have spring profiles load other profiles, you can do profile groups, but that is limited if you wanted something dynamic like enabling proxy settings. (this is maven profile adding a spring profile)
<profile>
<id>local-proxy</id>
<activation>
<property>
<name>env.http_proxy</name>
</property>
</activation>
<properties>
- <springBootRunArguments>--spring.profiles.include=PROXY,</springBootRunArguments>
+ <springBootRunArguments>--spring.config.import=classpath:application-PROXY.yml</springBootRunArguments>
</properties>
<build>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${maven-surefire-plugin.version}</version>
<configuration>
<systemPropertyVariables>
- <spring.profiles.include>PROXY</spring.profiles.include>
+ <spring.config.import>classpath:application-PROXY.yml</spring.config.import>
</systemPropertyVariables>
</configuration>
</plugin>
<plugin>
<artifactId>maven-failsafe-plugin</artifactId>
<configuration>
<systemPropertyVariables>
- <spring.profiles.include>PROXY</spring.profiles.include>
+ <spring.config.import>classpath:application-PROXY.yml</spring.config.import>
</systemPropertyVariables>
</configuration>
</plugin>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
- <jvmArguments>-Dspring-boot.run.jvmArguments='-Dspring.profiles.include="PROXY"'</jvmArguments>
+ <jvmArguments>-Dspring-boot.run.jvmArguments='-Dspring.config.import="classpath:application-PROXY.yml"'</jvmArguments>
</configuration>
</plugin>
</plugins>
</build>
</profile>
Any properties files you may have loaded that used "spring.profiles.include" can't be used any more with 2.4.x+ (unless you enabled legacy which will be going away after 2.6.x? version i believe)
-spring.profiles.include: defaults
+spring.config.import: classpath:application-defaults.yml
Also ensure that your bootstrap.yml has
aws.paramstore.enabled: true
It is on by default (But as its nowvin your config you can set it to false for local run's)
For more info, see:
https://spring.io/blog/2020/08/14/config-file-processing-in-spring-boot-2-4
https://github.com/awspring/spring-cloud-aws/blob/2.3.x/docs/src/main/asciidoc/parameter-store.adoc
https://stackoverflow.com/questions/64907675/including-profiles-in-spring-boot-2-4-0-version
Something I want to look into is setting up something like https://github.com/localstack/localstack within a maven project so that param store loading can be tested in pdev instead of being caught in an aws dev/test environment.
No comments:
Post a Comment