Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-1856

Port proxy-wasm-cpp-host to 2.3

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • Envoy
    • None
    • Sprint 55, Sprint 56

      Envoy 1.22 relies on an updated version of proxy-wasm-cpp-host: https://github.com/envoyproxy/envoy/blob/release/v1.22/bazel/repository_locations.bzl#L1093

       

      Since we maintain our own fork of it that works on OpenSSL, we need to update the fork with the latest changes from upstream. The rebase is not trivial and involves fixing some conflicts due to our OpenSSL and z/p changes.

       

      Our Envoy 2.3 is currently using the 2.2 code of proxy-wasm-cpp: https://github.com/maistra/envoy/blob/maistra-2.3/bazel/repository_locations.bzl#L1086

       

      Because of this we are getting failures when fetching the dependencies:

       
      ERROR: /tmp/tmp.WsNlyzXaqg/external/com_github_wasmtime/BUILD.bazel:17:20: no such package '@proxy_wasm_cpp_host//bazel/cargo/wasmtime': BUILD file not found in directory 'bazel/cargo/wasmtime' of external repository @proxy_wasm_cpp_host.
       
      

       

      We need to make sure to use the same version of proxy-wasm-cpp-host as Envoy 1.22. Note that the upstream PR that bumped the version changed two interconnected dependencies, but we only updated one: https://github.com/envoyproxy/envoy/pull/20711/files

       

            jsantana@redhat.com Jonh Wendell
            jsantana@redhat.com Jonh Wendell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: