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 }}
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
First, thanks for this module. I've been using it, along with your Consul module, to great effect for quite some time.
With the release of 1.4.1 I'm considering giving the new Vault Integrated Storage feature a go to determine if/where it's an appropriate alternative to a separate Consul storage backend.
I perused open feature requests and didn't see anything planned yet for this so just thought I'd ask before plotting my next move. If I head down this path before anyone else and there's interest, I'll gladly share any work I do to add support. If there's no interest in adding this feature to this module, that's good to know as well, along with the logic behind the decision. It may turn out that someone has already looked into this and determined that Consul (or S3) is still the better way to go in most production scenarios. My logic has otherwise been quite simple: the feature was released via 1.4.0 so wait until at least 1.4.1 before kicking the tires
Thanks again for all the great work you contribute. Cheers, be safe and be well.
Todd Michael
The text was updated successfully, but these errors were encountered:
A big +1 on adding this. It's definitely still early days, so we probably shouldn't recommend it as the default setup yet and wait for the feature to bake a bit longer, but a PR to make it easy to use that functionality is very welcome!
Hey guys,
First, thanks for this module. I've been using it, along with your Consul module, to great effect for quite some time.
With the release of
1.4.1
I'm considering giving the new Vault Integrated Storage feature a go to determine if/where it's an appropriate alternative to a separate Consul storage backend.I perused open feature requests and didn't see anything planned yet for this so just thought I'd ask before plotting my next move. If I head down this path before anyone else and there's interest, I'll gladly share any work I do to add support. If there's no interest in adding this feature to this module, that's good to know as well, along with the logic behind the decision. It may turn out that someone has already looked into this and determined that Consul (or S3) is still the better way to go in most production scenarios. My logic has otherwise been quite simple: the feature was released via
1.4.0
so wait until at least1.4.1
before kicking the tiresThanks again for all the great work you contribute. Cheers, be safe and be well.
Todd Michael
The text was updated successfully, but these errors were encountered: