Dave Syer
Dave Syer
As a user I'd expect to have something that worked in integration tests with `@SpringBootTest` as well as when I run my main method (changing the API of `SpringApplication` doesn't...
Just to complete that loop: if you define the initializer above as a standalone class and declare it in spring.factories it will work with `@SpringBootTest` and in a simple one-line...
What about an annotation instead of spring.factories, and a special component scan just for initializers and listeners? That's not even Spring 5 specific.
Spring Framework should do that itself then (easy to detect instances of its own interface being registered as `@Configuration`).
This issue was hijacked a bit by the Kotlin discussion. To set it back on course, here is a proof of concept for a way for Boot to support functional...
Thanks for the updates. I made a few comments. I'm sorry you gave up because it all works for me.
Why would the config server not be available? If it isn't wouldn't it be coming back again soon (so the existing retry behaviour should work fine)?
The SQS thing seems unrelated to this issue. Please open a new ticket (maybe in spring-cloud-aws?).
Please just open another issue. It's nothing to do with the config client if aws is trying to reload it at the wrong time.
/remove-lifecycle stale This is still definitely an issue.