8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm trying to upgrade one of our apps to Spring Boot 3.5.0 and spring-cloud-gcp 6.2.1.
According to the docs, you should no longer use the sm:// config suffix but rather sm@. So we've changed from this:
sm://
sm@
spring: application: name: my-aoo config: import: sm:// gcp: trace: enabled: true project-id: my-project rabbitmq: addresses: "${sm://rabbitmq_uri}"
to this:
spring: application: name: my-aoo config: import: sm@ gcp: trace: enabled: true project-id: my-project rabbitmq: addresses: "${sm@rabbitmq_uri}"
But now our application doesn't start when we're deploying to K8S:
*************************** APPLICATION FAILED TO START *************************** Description: Failed to bind properties under 'spring.rabbitmq' to org.springframework.boot.autoconfigure.amqp.RabbitProperties: Property: spring.rabbitmq.addresses Value: "${sm@rabbitmq_uri}" Origin: URL [file:config/application.yaml] - 29:16 Reason: java.lang.NumberFormatException: For input string: "" Action: Update your application's configuration
The text was updated successfully, but these errors were encountered:
I wonder if this is related: #3821
Sorry, something went wrong.
I also have the same issue.
No branches or pull requests
I'm trying to upgrade one of our apps to Spring Boot 3.5.0 and spring-cloud-gcp 6.2.1.
According to the docs, you should no longer use the
sm://
config suffix but rathersm@
. So we've changed from this:to this:
But now our application doesn't start when we're deploying to K8S:
The text was updated successfully, but these errors were encountered: