about Spring Cloud Vault Config Client, will it get all secrets in one go and load them as property source in environment once on startup, eagerly - or will it lazily load properties? if lazily, will it be one at a time or all of them together? either way, if secrets change on Vault, does that require restart of the app using vault config client?
I was considering bringing Spring Cloud Bus into my project but I see that since it uses Spring Cloud Stream and there are only binder implementations for Kafka and RabbitMQ, which I don’t particularly want to support in my AWS app. I’m wondering if a binder for SNS makes sense in the context of Spring Cloud Bus?