Is your feature request related to a problem? Please describe.
Update wasme's ABI version handling logic to use ABI versions (0_2_0, 0_2_1, etc) rather than the current commit hashes. As envoy-wasm has been upstreamed into envoy now, we can assume these versions will be more stable going forward.
For now we're keeping the old commit-hash versions from the envoy/envoy-wasm fork for backwards compatibility. These versions using the older syntax will be removed as support for those versions of Istio & Gloo are ended.
Sodman
commented
3 years ago
Is your feature request related to a problem? Please describe. Update wasme's ABI version handling logic to use ABI versions (0_2_0, 0_2_1, etc) rather than the current commit hashes. As envoy-wasm has been upstreamed into envoy now, we can assume these versions will be more stable going forward.
For now we're keeping the old commit-hash versions from the envoy/envoy-wasm fork for backwards compatibility. These versions using the older syntax will be removed as support for those versions of Istio & Gloo are ended.
Additional context Latest Gloo 1.5.x release uses v0_2_1, Istio 1.7.2 uses v0_2_0.