wu-sheng opened a new pull request, #30: URL: https://github.com/apache/skywalking-graalvm-distro/pull/30
### Sync upstream to `89624809f0` and adopt the upstream swctl `admin` e2e migration Advances the `skywalking/` submodule `ad733554b0` → `89624809f0` (4 commits — docs + e2e only, **no production code**). The notable upstream change is **#13889**, which migrated the e2e admin-API calls from raw `curl` to the new `swctl admin ...` command tree and bumped `skywalking-cli` to an admin-capable build. This PR brings that into the distro. #### What changed - **`SW_CTL_COMMIT`** `9a1beab0` → `b447211a` (admin-capable swctl) in `test/e2e/script/env`. Backward-compatible: the existing `metrics exec` / `service ls` / … commands used by the other reused e2e cases are unchanged; the `admin` command tree is purely additive (verified against the built binary). - **`live-debugging` e2e** now drives the admin checks through `swctl admin dsl-debug` / `runtime-rule` / `oal` *alongside* the existing raw-curl HTTP-contract cases. This distro serves a structured **HTTP 501** for `/dsl-debugging/*` and `/runtime/*` (a closed-world native image can't do runtime MAL/LAL/OAL codegen), so swctl exits non-zero and logs its typed error envelope; the new cases grep back `httpStatus` + `error` code + `feature` root, proving the official CLI surfaces a clean *"unsupported"* (`feature_not_available_in_graalvm_native`) instead of crashing or a confusing 404. The case setup now installs swctl. - Docs: `version-mapping.md` dev row + `changes/changes.md`. #### Verification - [x] `make compile` — BUILD SUCCESS - [x] `license-eye header check` — 0 invalid - [x] `verify-version-mapping.sh` — all mappings verified - [x] swctl `b447211` output empirically validated against a mock of the distro's 501 stub: all five `admin` commands resolve to the expected `httpStatus: 501` / `error` / `feature` - [ ] CI: unit tests, native amd64/arm64, e2e (incl. `live-debugging`) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
