Repository navigation
chore(deps): update hashicorp/consul docker tag to v2.1 - #59
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #59 +/- ##
=======================================
Coverage 97.48% 97.48%
=======================================
Files 13 13
Lines 438 438
=======================================
Hits 427 427
Misses 11 11 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
2.0→2.12.0→2.1Release Notes
hashicorp/consul
v2.1BREAKING CHANGES:
/v1/configwrites that previously succeeded can now fail. Raise the limit with the newlimits.http_max_request_body_sizesetting if needed./api/...) request bodies are now subject to the samelimits.http_max_request_body_sizelimit (512 KiB by default), and oversized requests return HTTP 413.GET /v1/agent/connect/ca/leaf/:servicenow requiresservice:writeon the requested service for every request, including requests served from the agent's cached leaf certificate. Requests with no token or a token without that permission now receive HTTP 403 instead of the cached certificate. Callers must present a token withservice:writefor the service.Catalog.Registernow requires write permission on the node or service of an existing health check when updating it. Tokens that previously updated checks without that permission now receive a permission denied error.SECURITY:
apk upgradewhen building the Alpine-based container images so base-image packages (such as sqlite and jq) are up to date. [GH-23964]IMPROVEMENTS:
BUG FIXES:
Proxy.Configand per-upstream config so it follows the same case-folding rules as the config decoders. Keys that differ only by Unicode case folding (for exampleenvoy_local_cluſter_json), and Go field-name forms such asEnvoyListenerJSON, now requiremesh:writelike their canonical spellings./v1/k%76/...), and skips/v1/txnbodies.POST /v1/operator/audit-hashnow returns HTTP 413 for oversized bodies.PUT /v1/kv/so chunked request bodies are bounded bykv_max_value_size, matching the existingContent-Lengthcheck.hashicorpmetricstag. [GH-23813]Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.