Migrate deprecated Envoy v2 gzip compression API to v3 #462
+2
−2
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.
Summary
This PR migrates the last remaining usage of deprecated Envoy v2 API to the modern v3 API in the compression filter factory.
Problem
The codebase was still using a deprecated v2 import for gzip compression level constants:
This usage was in the fallback case when compression quality configuration is not provided:
Solution
Updated the code to use the v3 API equivalent:
The migration maintains identical behavior since both
v2.BEST_VALUEandv3.BEST_SPEEDhave the same numeric value (1), representing the fastest compression level.Changes
io.envoyproxy.envoy.config.filter.http.gzip.v2.Gzip.CompressionLevel.Enum.BEST_VALUEGzip.CompressionLevel.BEST_SPEEDdirectlyVerification
The codebase now exclusively uses modern Envoy v3 APIs with no deprecated dependencies.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.