Tom Proctor

This was filed earlier, but I commented on #151 which shares a lot in common with this issue. I'd be interested to get thoughts on my comment there, as it...

Hi @developer-guy, please can you include some documentation and rationale in the Makefile for those options?

Hi @developer-guy, please can you put the reasoning in the code alongside/just before the usage? * `-buildid=` - I'm not convinced the need for this one is proven. It's set...

I've commented on #150, which is fairly straightforward in terms of design. It's pretty obvious the TTL should be respected and we'll fix that - I think in most deployment...

Thanks for opening this with lots of details. It's still a work in progress, but I'd like to combine #163 and https://github.com/hashicorp/vault-helm/pull/749 to address a lot of the pain points....

Thanks for raising, that's a good idea. I'll see if we can get that added to the release targets.

We don't have any firm timeline on this, but we have discussed this internally and want to add it. Thanks for raising it, it's really helpful to get an idea...

Hi @thomas-riccardi, thanks for the feedback! We are indeed planning something in this area. The likely route is that we will do #82 first, and then start deploying Vault Agent...

@jonpjenkins yep I've been thinking about this quite a bit lately. Adding lease renewal should now be relatively straightforward, and I think it probably won't even require any further changes...

For anyone following this issue, #163 and https://github.com/hashicorp/vault-helm/pull/749 are relevant. It's not quite the whole picture, but they should be good steps forward when merged.