Open v-ladynev opened 3 years ago
this was created before spring boot changed the default of bean overriding. The docs could be updated to reflect primary as an option. I don't understand how a wrapper will help.
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
@spencergibb Maybe a wrapper will not help. I just wanted to say that spring-vault
has a separate TaskScheduler
that doesn't influence my application scheduling logic at all. spring-cloud-consul
does it.
After chatting with the team in the spring cloud kubernetes issue, we're doing a wrapper as a bean, we should do the same here.
This issue related to #146. A fix provided there is not suitable. For example:
TaskScheduler
with 2 threads works well.To fix this a
spring-vault
approach withTaskSchedulerWrapper
can be used https://github.com/spring-projects/spring-vault/blob/main/spring-vault-core/src/main/java/org/springframework/vault/config/AbstractVaultConfiguration.java#L324The advise in the documentation is not very good:
TaskScheduler
?The simplest workaround is not to use a bean with the same name, but
@Primary
on the application configuration.