-
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
Backport of Updated consul-template version into release/1.16.x #26865
Backport of Updated consul-template version into release/1.16.x #26865
Conversation
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes 1 out of 2 committers have signed the CLA.
temp seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
CI Results: failed ❌ |
Build Results: |
@divyaac could you please manually backport this PR? Failing the CLA check means that the auto backport was not successful. |
…rsion/forcibly-evolved-walleye
d2937ad
to
ca5eaea
Compare
ca5eaea
to
0b92030
Compare
…rsion/forcibly-evolved-walleye
Closing this because we no longer backport to CE this far along. |
Pull request was closed
Backport
This PR is auto-generated from #26863 to be assessed for backporting due to the inclusion of the label backport/1.16.x.
🚨
The person who merged in the original PR is:
@divyaac
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
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.
Overview of commits