You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Config Server + Config Vault + Actuator = two beans with the same name #740
spring-cloud-config-server, spring-cloud-starter-vault-config and starter-actuator on the classpath we get the issue that the bean vaultTemplate is defined in SpringVaultClientConfiguration and in VaultAutoConfiguration. The application will not start unless we provide bean overriding.
It's enough to rename one of those beans to fix this.
But SpringVaultClientConfiguration does not have any beans defined in it. I searched spring cloud config for anything named vaultTemplate but I did not find any beans with that name.
Activity
ryanjbaxter commentedon Dec 18, 2024
I see
vaultTemplatedefined here https://github.com/spring-cloud/spring-cloud-vault/blob/main/spring-cloud-vault-config/src/main/java/org/springframework/cloud/vault/config/VaultAutoConfiguration.java#L158But
SpringVaultClientConfigurationdoes not have any beans defined in it. I searched spring cloud config for anything namedvaultTemplatebut I did not find any beans with that name.marcingrzejszczak commentedon Dec 19, 2024
SpringVaultClientConfigurationextendsAbstractVaultConfiguration.vaultTemplateis defined here.The second one is indeed here.
ryanjbaxter commentedon Dec 19, 2024
But these are in Spring Vault Core and Spring Cloud Vault, so shouldn't the problem be resolved in one of those projects?
marcingrzejszczak commentedon Dec 19, 2024
That's a very valid point ;) Let's transfer this to Spring Cloud Vault.