Backport of Bump consul-template 0.32.0 -> 0.33.0 into release/1.14.x #22337
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #22322 to be assessed for backporting due to the inclusion of the label backport/1.14.x.
🚨
The person who merged in the original PR is:
@tomhjp
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.
Bumps consul-template to v0.33.0. Changelog
In particular this pulls in hashicorp/consul-template#1782 to ensure the environment variable
VAULT_CACERT_BYTES
works equally well in both Vault Agent auto auth and Vault Agent templating, whereas previously it only worked for the former.I've added a test for VAULT_CACERT_BYTES, and while it used a lot of copy-paste from the test
TestAgent_Template_Basic
, I also took some time to extract some common AppRole + KV setup from other tests into one consolidated function to reduce duplication.Overview of commits