Kong 3.7.1 Bazel build fails

[jeremyjpj0916]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.7.1

Current Behavior

Did yall delete a repo/release/files in newer Kong that makes builds not possible from bazel in older 3.x versions?

If so, can repo be restored or I get the files Kong needs on 3.7.1 from that old repo to point bazel at it somehow and where that edit would need to be?

#32 60.41 (14:28:06) WARNING: Download from https://github.com/Kong/datakit-filter/releases/download/0.1.0/datakit.meta.json failed: class java.io.FileNotFoundException GET returned 404 Not Found
[5345](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5346)#32 60.41 (14:28:06) INFO: Repository datakit.meta.json instantiated at:
[5346](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5347)#32 60.41   /kong/WORKSPACE:37:23: in <toplevel>
[5347](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5348)#32 60.41   /kong/build/openresty/repositories.bzl:29:30: in openresty_repositories
[5348](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5349)#32 60.41   /kong/build/openresty/wasmx/filters/repositories.bzl:10:18: in wasm_filters_repositories
[5349](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5350)#32 60.41   /root/.cache/bazel/_bazel_root/d5742f123fe1fc789bc2468bf73ca667/external/bazel_tools/tools/build_defs/repo/utils.bzl:268:18: in maybe
[5350](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5351)#32 60.41 Repository rule http_file defined at:
[5351](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5352)#32 60.41   /root/.cache/bazel/_bazel_root/d5742f123fe1fc789bc2468bf73ca667/external/bazel_tools/tools/build_defs/repo/http.bzl:473:28: in <toplevel>
[5352](https://github.com/optum-eeps/sg-base-image/actions/runs/13015709269/job/36357403963#step:3:5353)#32 60.42 (14:28:06) WARNING: Download from https://github.com/Kong/datakit-filter/releases/download/0.1.0/datakit.wasm failed: class java.io.FileNotFoundException GET returned 404 Not Found

Seems so, but did yall realize it would break building older versions of Kong?

• Wasm: Removed the experimental datakit Wasm filter
  #14012
  KAG-6021

And google cache still shows used to be there(but now 404s):

If yall have an alternative way to build 3.7.1 let me know, we don't even use the wasm capabilities too if there is a better way to disable that in the build flow.

Best,
Jeremy

[jeremyjpj0916]

To avoid things like this in the ci/cd may want to write logic in Kongs build/deploy process that tests building 2-3 versions back of Kong too with the modern build to ensure no regression of builds for older Kong versions. Or perhaps that at least can keep it so builds/versions created within the last year continue to succeed.