-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated consul-template version #26863
Conversation
I think it's necessary, since it affects the way Agent works, and some customers may be on the lookout for the bug fix in a Vault version. It's unlikely that Vault customers are looking at consul-template release notes, and they may not be aware that consul template powers Agent's template engine. We might want to backport this to 1.16, too (since LTS)! |
CI Results: |
Build Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I think we should remove the sentence about consul-template in the changelog but that's non-blocking and optional.
Co-authored-by: Violet Hynes <[email protected]>
Thought about it, and didn't add a changelog because technically the change was in consul-template, not in Vault? There's a changelog there to reflect that.
If you think it's necessary, I can add a changelog here as well.