MINOR: Fix JDK version and architecture parameters in system test worker provisioning by tirthooo7 · Pull Request #21394 · apache/kafka

tirthooo7 · 2026-02-03T06:37:45Z

Summary

Fixes bugs where --jdk-version and --jdk-arch parameters were ignored during system test worker provisioning, and refactors vagrant/base.sh to support flexible JDK versions without code changes.

Problem

The Vagrant provisioning script (vagrant/base.sh) had two bugs that caused JDK version parameters to be ignored:

Bug	Problem
#1: `--jdk-version` ignored	`JDK_FULL` was hardcoded to `17-linux-x64`, so passing `--jdk-version 25` still downloaded JDK 17
#2: `--jdk-arch` ignored	Architecture parameter was passed but never used in the S3 download URL

Solution

Validate JDK_MAJOR and JDK_ARCH input parameters with regex
Dynamically construct JDK_FULL from JDK_MAJOR and JDK_ARCH
Update S3 path to use /jdk/ subdirectory
Add logging for debugging

Changes

`vagrant/base.sh`

Change	Description
Input validation	Added regex validation for `JDK_MAJOR` and `JDK_ARCH` with sensible defaults
Dynamic construction	`JDK_FULL` is now constructed from `JDK_MAJOR` and `JDK_ARCH` if not explicitly provided
Updated S3 path	Changed URL from `/kafka-packages/jdk-{version}.tar.gz` to `/kafka-packages/jdk/jdk-{version}.tar.gz`
Logging	Added debug output for JDK configuration
Backward compatibility	Vagrantfile can still pass `JDK_FULL` directly; the script validates and uses it if valid

S3 Path Change

Old Path

s3://kafka-packages/jdk-{version}.tar.gz

New Path

s3://kafka-packages/jdk/jdk-{version}.tar.gz

Available JDKs in `s3://kafka-packages/jdk/`

File	Version	Architecture
`jdk-7u80-linux-x64.tar.gz`	7u80	x64
`jdk-8u144-linux-x64.tar.gz`	8u144	x64
`jdk-8u161-linux-x64.tar.gz`	8u161	x64
`jdk-8u171-linux-x64.tar.gz`	8u171	x64
`jdk-8u191-linux-x64.tar.gz`	8u191	x64
`jdk-8u202-linux-x64.tar.gz`	8u202	x64
`jdk-11.0.2-linux-x64.tar.gz`	11.0.2	x64
`jdk-17-linux-x64.tar.gz`	17	x64
`jdk-18.0.2-linux-x64.tar.gz`	18.0.2	x64
`jdk-21.0.1-linux-x64.tar.gz`	21.0.1	x64
`jdk-21.0.1-linux-aarch64.tar.gz`	21.0.1	aarch64
`jdk-25-linux-x64.tar.gz`	25	x64
`jdk-25-linux-aarch64.tar.gz`	25	aarch64
`jdk-25.0.1-linux-x64.tar.gz`	25.0.1	x64
`jdk-25.0.1-linux-aarch64.tar.gz`	25.0.1	aarch64
`jdk-25.0.2-linux-x64.tar.gz`	25.0.2	x64
`jdk-25.0.2-linux-aarch64.tar.gz`	25.0.2	aarch64

Future JDK Releases

IMPORTANT: No code changes required for future Java major/minor releases!

The validation regex supports all version formats:

Major versions: 17, 25, 26
Minor versions: 25.0.1, 25.0.2, 26.0.1
Legacy format: 8u144, 8u202

Adding New JDK Versions

To add support for a new JDK version (e.g., JDK 26, 25.0.3):

Download the JDK tarball from Oracle/Adoptium
Rename to follow naming convention: jdk-{VERSION}-linux-{ARCH}.tar.gz
Upload to S3: aws s3 cp jdk-{VERSION}-linux-{ARCH}.tar.gz s3://kafka-packages/jdk/
Use in tests: --jdk-version {VERSION} --jdk-arch {ARCH}

No modifications to base.sh or any other scripts are needed.

Benefits

Before	After
`--jdk-version` ignored	✅ Correctly uses specified version
`--jdk-arch` ignored	✅ Correctly uses specified architecture
Only major version support	✅ Full version support (e.g., `25.0.2`)
Code change needed for new JDK	✅ Just upload to S3 and pass version

Testing

Tested with different JDK versions to confirm the fix works correctly:

Test	JDK_MAJOR	Expected	Actual	Result	Test Report
JDK 17	`17`	javac 17.0.4	javac 17.0.4	✅	Report
JDK 25	`25`	javac 25.0.2	javac 25.0.2	✅	Report

Backward Compatibility

Vagrantfile: Continues to work as before
Existing workflows: Default behavior unchanged (JDK 17 on x64 architecture)
No breaking changes: All existing configurations continue to work

Reviewers

@chia7712 @omkreddy

…antfile

…e error handling

…nk-ak

chia7712

@tirthooo7 thanks for your contribution. You are a lifesaver for our Vagrant

chia7712 · 2026-02-10T17:43:13Z

vagrant/base.sh


-JDK_MAJOR="${JDK_MAJOR:-17}"
-JDK_FULL="${JDK_FULL:-17-linux-x64}"
+# Validate JDK_MAJOR - must be a version number (e.g., 8u144, 17, 25.0.1), default to 17 if empty or invalid


kafka does not support JDK8 any more.

chia7712 · 2026-02-10T17:47:07Z

vagrant/base.sh

+
+# Validate JDK_ARCH - default to x64 if empty or invalid
+if [[ -z "$JDK_ARCH" || ! "$JDK_ARCH" =~ ^(x64|aarch64)$ ]]; then
+    JDK_ARCH="x64"


Should we either throw an exception or log a warning if the format is invalid?

We want to avoid breaking any existing workflows, so I don’t think we should throw an exception here. Defaulting to this behavior makes sense, but I can add a warning log to flag the invalid format.

…se.sh

tirthooo7 · 2026-02-11T03:40:55Z

hi @chia7712 I have added the warning logs , can you review it again ?

…ker provisioning (apache#21394) ## Summary Fixes bugs where `--jdk-version` and `--jdk-arch` parameters were ignored during system test worker provisioning, and refactors `vagrant/base.sh` to support flexible JDK versions without code changes. --- ## Problem The Vagrant provisioning script (`vagrant/base.sh`) had two bugs that caused JDK version parameters to be ignored: | Bug | Problem | |-----|---------| | **#1: `--jdk-version` ignored** | `JDK_FULL` was hardcoded to `17-linux-x64`, so passing `--jdk-version 25` still downloaded JDK 17 | | **#2: `--jdk-arch` ignored** | Architecture parameter was passed but never used in the S3 download URL | --- ## Solution - Validate `JDK_MAJOR` and `JDK_ARCH` input parameters with regex - Dynamically construct `JDK_FULL` from `JDK_MAJOR` and `JDK_ARCH` - Update S3 path to use `/jdk/` subdirectory - Add logging for debugging --- ## Changes ### `vagrant/base.sh` | Change | Description | |--------|-------------| | **Input validation** | Added regex validation for `JDK_MAJOR` and `JDK_ARCH` with sensible defaults | | **Dynamic construction** | `JDK_FULL` is now constructed from `JDK_MAJOR` and `JDK_ARCH` if not explicitly provided | | **Updated S3 path** | Changed URL from `/kafka-packages/jdk-{version}.tar.gz` to `/kafka-packages/jdk/jdk-{version}.tar.gz` | | **Logging** | Added debug output for JDK configuration | | **Backward compatibility** | Vagrantfile can still pass `JDK_FULL` directly; the script validates and uses it if valid | --- ## S3 Path Change ### Old Path ``` s3://kafka-packages/jdk-{version}.tar.gz ``` ### New Path ``` s3://kafka-packages/jdk/jdk-{version}.tar.gz ``` ### Available JDKs in `s3://kafka-packages/jdk/` | File | Version | Architecture | |------|---------|--------------| | `jdk-7u80-linux-x64.tar.gz` | 7u80 | x64 | | `jdk-8u144-linux-x64.tar.gz` | 8u144 | x64 | | `jdk-8u161-linux-x64.tar.gz` | 8u161 | x64 | | `jdk-8u171-linux-x64.tar.gz` | 8u171 | x64 | | `jdk-8u191-linux-x64.tar.gz` | 8u191 | x64 | | `jdk-8u202-linux-x64.tar.gz` | 8u202 | x64 | | `jdk-11.0.2-linux-x64.tar.gz` | 11.0.2 | x64 | | `jdk-17-linux-x64.tar.gz` | 17 | x64 | | `jdk-18.0.2-linux-x64.tar.gz` | 18.0.2 | x64 | | `jdk-21.0.1-linux-x64.tar.gz` | 21.0.1 | x64 | | `jdk-21.0.1-linux-aarch64.tar.gz` | 21.0.1 | aarch64 | | `jdk-25-linux-x64.tar.gz` | 25 | x64 | | `jdk-25-linux-aarch64.tar.gz` | 25 | aarch64 | | `jdk-25.0.1-linux-x64.tar.gz` | 25.0.1 | x64 | | `jdk-25.0.1-linux-aarch64.tar.gz` | 25.0.1 | aarch64 | | `jdk-25.0.2-linux-x64.tar.gz` | 25.0.2 | x64 | | `jdk-25.0.2-linux-aarch64.tar.gz` | 25.0.2 | aarch64 | --- ## Future JDK Releases > **IMPORTANT: No code changes required for future Java major/minor releases!** The validation regex supports all version formats: - **Major versions**: `17`, `25`, `26` - **Minor versions**: `25.0.1`, `25.0.2`, `26.0.1` - **Legacy format**: `8u144`, `8u202` ### Adding New JDK Versions To add support for a new JDK version (e.g., JDK 26, 25.0.3): 1. Download the JDK tarball from Oracle/Adoptium 2. Rename to follow naming convention: `jdk-{VERSION}-linux-{ARCH}.tar.gz` 3. Upload to S3: `aws s3 cp jdk-{VERSION}-linux-{ARCH}.tar.gz s3://kafka-packages/jdk/` 4. Use in tests: `--jdk-version {VERSION} --jdk-arch {ARCH}` No modifications to `base.sh` or any other scripts are needed. --- ## Benefits | Before | After | |--------|-------| | `--jdk-version` ignored | ✅ Correctly uses specified version | | `--jdk-arch` ignored | ✅ Correctly uses specified architecture | | Only major version support | ✅ Full version support (e.g., `25.0.2`) | | Code change needed for new JDK | ✅ Just upload to S3 and pass version | --- ## Testing Tested with different JDK versions to confirm the fix works correctly: | Test | JDK_MAJOR | Expected | Actual | Result | Test Report | |------|-----------|----------|--------|--------|-------------| | JDK 17 | `17` | javac 17.0.4 | javac 17.0.4 | ✅ | | JDK 25 | `25` | javac 25.0.2 | javac 25.0.2 | ✅ | --- ## Backward Compatibility - **Vagrantfile**: Continues to work as before - **Existing workflows**: Default behavior unchanged (JDK 17 on x64 architecture) - **No breaking changes**: All existing configurations continue to work --- Reviewers: Manikumar Reddy <manikumar.reddy@gmail.com>, Chia-Ping Tsai <chia7712@gmail.com>

…ker provisioning (apache#21394) Fixes bugs where `--jdk-version` and `--jdk-arch` parameters were ignored during system test worker provisioning, and refactors `vagrant/base.sh` to support flexible JDK versions without code changes. --- The Vagrant provisioning script (`vagrant/base.sh`) had two bugs that caused JDK version parameters to be ignored: | Bug | Problem | |-----|---------| | **#1: `--jdk-version` ignored** | `JDK_FULL` was hardcoded to `17-linux-x64`, so passing `--jdk-version 25` still downloaded JDK 17 | | **#2: `--jdk-arch` ignored** | Architecture parameter was passed but never used in the S3 download URL | --- - Validate `JDK_MAJOR` and `JDK_ARCH` input parameters with regex - Dynamically construct `JDK_FULL` from `JDK_MAJOR` and `JDK_ARCH` - Update S3 path to use `/jdk/` subdirectory - Add logging for debugging --- | Change | Description | |--------|-------------| | **Input validation** | Added regex validation for `JDK_MAJOR` and `JDK_ARCH` with sensible defaults | | **Dynamic construction** | `JDK_FULL` is now constructed from `JDK_MAJOR` and `JDK_ARCH` if not explicitly provided | | **Updated S3 path** | Changed URL from `/kafka-packages/jdk-{version}.tar.gz` to `/kafka-packages/jdk/jdk-{version}.tar.gz` | | **Logging** | Added debug output for JDK configuration | | **Backward compatibility** | Vagrantfile can still pass `JDK_FULL` directly; the script validates and uses it if valid | --- ``` s3://kafka-packages/jdk-{version}.tar.gz ``` ``` s3://kafka-packages/jdk/jdk-{version}.tar.gz ``` | File | Version | Architecture | |------|---------|--------------| | `jdk-7u80-linux-x64.tar.gz` | 7u80 | x64 | | `jdk-8u144-linux-x64.tar.gz` | 8u144 | x64 | | `jdk-8u161-linux-x64.tar.gz` | 8u161 | x64 | | `jdk-8u171-linux-x64.tar.gz` | 8u171 | x64 | | `jdk-8u191-linux-x64.tar.gz` | 8u191 | x64 | | `jdk-8u202-linux-x64.tar.gz` | 8u202 | x64 | | `jdk-11.0.2-linux-x64.tar.gz` | 11.0.2 | x64 | | `jdk-17-linux-x64.tar.gz` | 17 | x64 | | `jdk-18.0.2-linux-x64.tar.gz` | 18.0.2 | x64 | | `jdk-21.0.1-linux-x64.tar.gz` | 21.0.1 | x64 | | `jdk-21.0.1-linux-aarch64.tar.gz` | 21.0.1 | aarch64 | | `jdk-25-linux-x64.tar.gz` | 25 | x64 | | `jdk-25-linux-aarch64.tar.gz` | 25 | aarch64 | | `jdk-25.0.1-linux-x64.tar.gz` | 25.0.1 | x64 | | `jdk-25.0.1-linux-aarch64.tar.gz` | 25.0.1 | aarch64 | | `jdk-25.0.2-linux-x64.tar.gz` | 25.0.2 | x64 | | `jdk-25.0.2-linux-aarch64.tar.gz` | 25.0.2 | aarch64 | --- > **IMPORTANT: No code changes required for future Java major/minor releases!** The validation regex supports all version formats: - **Major versions**: `17`, `25`, `26` - **Minor versions**: `25.0.1`, `25.0.2`, `26.0.1` - **Legacy format**: `8u144`, `8u202` To add support for a new JDK version (e.g., JDK 26, 25.0.3): 1. Download the JDK tarball from Oracle/Adoptium 2. Rename to follow naming convention: `jdk-{VERSION}-linux-{ARCH}.tar.gz` 3. Upload to S3: `aws s3 cp jdk-{VERSION}-linux-{ARCH}.tar.gz s3://kafka-packages/jdk/` 4. Use in tests: `--jdk-version {VERSION} --jdk-arch {ARCH}` No modifications to `base.sh` or any other scripts are needed. --- | Before | After | |--------|-------| | `--jdk-version` ignored | ✅ Correctly uses specified version | | `--jdk-arch` ignored | ✅ Correctly uses specified architecture | | Only major version support | ✅ Full version support (e.g., `25.0.2`) | | Code change needed for new JDK | ✅ Just upload to S3 and pass version | --- Tested with different JDK versions to confirm the fix works correctly: | Test | JDK_MAJOR | Expected | Actual | Result | Test Report | |------|-----------|----------|--------|--------|-------------| | JDK 17 | `17` | javac 17.0.4 | javac 17.0.4 | ✅ | | JDK 25 | `25` | javac 25.0.2 | javac 25.0.2 | ✅ | --- - **Vagrantfile**: Continues to work as before - **Existing workflows**: Default behavior unchanged (JDK 17 on x64 architecture) - **No breaking changes**: All existing configurations continue to work --- Reviewers: Manikumar Reddy <manikumar.reddy@gmail.com>, Chia-Ping Tsai <chia7712@gmail.com>

…ker provisioning (#21394) ## Summary Fixes bugs where `--jdk-version` and `--jdk-arch` parameters were ignored during system test worker provisioning, and refactors `vagrant/base.sh` to support flexible JDK versions without code changes. --- ## Problem The Vagrant provisioning script (`vagrant/base.sh`) had two bugs that caused JDK version parameters to be ignored: | Bug | Problem | |-----|---------| | **#1: `--jdk-version` ignored** | `JDK_FULL` was hardcoded to `17-linux-x64`, so passing `--jdk-version 25` still downloaded JDK 17 | | **#2: `--jdk-arch` ignored** | Architecture parameter was passed but never used in the S3 download URL | --- ## Solution - Validate `JDK_MAJOR` and `JDK_ARCH` input parameters with regex - Dynamically construct `JDK_FULL` from `JDK_MAJOR` and `JDK_ARCH` - Update S3 path to use `/jdk/` subdirectory - Add logging for debugging --- ## Changes ### `vagrant/base.sh` | Change | Description | |--------|-------------| | **Input validation** | Added regex validation for `JDK_MAJOR` and `JDK_ARCH` with sensible defaults | | **Dynamic construction** | `JDK_FULL` is now constructed from `JDK_MAJOR` and `JDK_ARCH` if not explicitly provided | | **Updated S3 path** | Changed URL from `/kafka-packages/jdk-{version}.tar.gz` to `/kafka-packages/jdk/jdk-{version}.tar.gz` | | **Logging** | Added debug output for JDK configuration | | **Backward compatibility** | Vagrantfile can still pass `JDK_FULL` directly; the script validates and uses it if valid | --- ## S3 Path Change ### Old Path ``` s3://kafka-packages/jdk-{version}.tar.gz ``` ### New Path ``` s3://kafka-packages/jdk/jdk-{version}.tar.gz ``` ### Available JDKs in `s3://kafka-packages/jdk/` | File | Version | Architecture | |------|---------|--------------| | `jdk-7u80-linux-x64.tar.gz` | 7u80 | x64 | | `jdk-8u144-linux-x64.tar.gz` | 8u144 | x64 | | `jdk-8u161-linux-x64.tar.gz` | 8u161 | x64 | | `jdk-8u171-linux-x64.tar.gz` | 8u171 | x64 | | `jdk-8u191-linux-x64.tar.gz` | 8u191 | x64 | | `jdk-8u202-linux-x64.tar.gz` | 8u202 | x64 | | `jdk-11.0.2-linux-x64.tar.gz` | 11.0.2 | x64 | | `jdk-17-linux-x64.tar.gz` | 17 | x64 | | `jdk-18.0.2-linux-x64.tar.gz` | 18.0.2 | x64 | | `jdk-21.0.1-linux-x64.tar.gz` | 21.0.1 | x64 | | `jdk-21.0.1-linux-aarch64.tar.gz` | 21.0.1 | aarch64 | | `jdk-25-linux-x64.tar.gz` | 25 | x64 | | `jdk-25-linux-aarch64.tar.gz` | 25 | aarch64 | | `jdk-25.0.1-linux-x64.tar.gz` | 25.0.1 | x64 | | `jdk-25.0.1-linux-aarch64.tar.gz` | 25.0.1 | aarch64 | | `jdk-25.0.2-linux-x64.tar.gz` | 25.0.2 | x64 | | `jdk-25.0.2-linux-aarch64.tar.gz` | 25.0.2 | aarch64 | --- ## Future JDK Releases > **IMPORTANT: No code changes required for future Java major/minor releases!** The validation regex supports all version formats: - **Major versions**: `17`, `25`, `26` - **Minor versions**: `25.0.1`, `25.0.2`, `26.0.1` - **Legacy format**: `8u144`, `8u202` ### Adding New JDK Versions To add support for a new JDK version (e.g., JDK 26, 25.0.3): 1. Download the JDK tarball from Oracle/Adoptium 2. Rename to follow naming convention: `jdk-{VERSION}-linux-{ARCH}.tar.gz` 3. Upload to S3: `aws s3 cp jdk-{VERSION}-linux-{ARCH}.tar.gz s3://kafka-packages/jdk/` 4. Use in tests: `--jdk-version {VERSION} --jdk-arch {ARCH}` No modifications to `base.sh` or any other scripts are needed. --- ## Benefits | Before | After | |--------|-------| | `--jdk-version` ignored | ✅ Correctly uses specified version | | `--jdk-arch` ignored | ✅ Correctly uses specified architecture | | Only major version support | ✅ Full version support (e.g., `25.0.2`) | | Code change needed for new JDK | ✅ Just upload to S3 and pass version | --- ## Testing Tested with different JDK versions to confirm the fix works correctly: | Test | JDK_MAJOR | Expected | Actual | Result | Test Report | |------|-----------|----------|--------|--------|-------------| | JDK 17 | `17` | javac 17.0.4 | javac 17.0.4 | ✅ | | JDK 25 | `25` | javac 25.0.2 | javac 25.0.2 | ✅ | --- ## Backward Compatibility - **Vagrantfile**: Continues to work as before - **Existing workflows**: Default behavior unchanged (JDK 17 on x64 architecture) - **No breaking changes**: All existing configurations continue to work --- Reviewers: Manikumar Reddy <manikumar.reddy@gmail.com>, Chia-Ping Tsai <chia7712@gmail.com>

MINOR: Update JDK fetch logic for version 25 and improve path handling

45bafdd

github-actions bot added tools small Small PRs triage PRs from the community labels Feb 3, 2026

tirthooo7 added 8 commits February 4, 2026 21:57

MINOR: Add additional AWS tags for better resource management in Vagr…

6d784ca

…antfile

MINOR: Add default AWS tags for SCP compliance in Vagrantfile

e265712

MINOR: Refactor JDK fetch logic for unified path structure and improv…

7df8ea6

…e error handling

Revert cflt tagging

e8da59b

Merge remote-tracking branch 'upstream/trunk' into jdk-25-upgrade-tru…

03b7b9a

…nk-ak

MINOR: Update JDK fetch logic and improve validation in base.sh

a65e78c

Merge branch 'apache-trunk' into jdk-25-upgrade-trunk-ak

b720615

MINOR: Remove unnecessary export of DEBIAN_FRONTEND in base.sh

cbd986a

tirthooo7 changed the title ~~MINOR: Update JDK fetch logic for version 25 and improve path handling~~ MINOR: Fix JDK version and architecture parameters in system test worker provisioning Feb 10, 2026

tirthooo7 marked this pull request as ready for review February 10, 2026 16:11

chia7712 reviewed Feb 10, 2026

View reviewed changes

MINOR: Enhance JDK validation with warnings for invalid formats in ba…

f5f5d48

…se.sh

tirthooo7 requested a review from chia7712 February 10, 2026 18:02

github-actions bot removed the triage PRs from the community label Feb 11, 2026

omkreddy approved these changes Feb 11, 2026

View reviewed changes

chia7712 approved these changes Feb 11, 2026

View reviewed changes

omkreddy merged commit dc5fd6c into apache:trunk Feb 12, 2026
20 checks passed

omkreddy deleted the jdk-25-upgrade-trunk-ak branch February 12, 2026 03:27

tirthooo7 mentioned this pull request Feb 12, 2026

MINOR: Fix JDK version and architecture parameters in system test worker provisioning #21466

Closed

tirthooo7 mentioned this pull request Feb 13, 2026

MINOR: Fix JDK version, architecture parameters and SSL certificate verification in system tes confluentinc/kafka#1907

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MINOR: Fix JDK version and architecture parameters in system test worker provisioning#21394

MINOR: Fix JDK version and architecture parameters in system test worker provisioning#21394
omkreddy merged 10 commits intoapache:trunkfrom
confluentinc:jdk-25-upgrade-trunk-ak

tirthooo7 commented Feb 3, 2026 •

edited

Loading

Uh oh!

chia7712 left a comment

Uh oh!

chia7712 Feb 10, 2026

Uh oh!

chia7712 Feb 10, 2026

Uh oh!

tirthooo7 Feb 10, 2026

Uh oh!

tirthooo7 commented Feb 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

tirthooo7 commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Problem

Solution

Changes

vagrant/base.sh

S3 Path Change

Old Path

New Path

Available JDKs in s3://kafka-packages/jdk/

Future JDK Releases

Adding New JDK Versions

Benefits

Testing

Backward Compatibility

Reviewers

Uh oh!

chia7712 left a comment

Choose a reason for hiding this comment

Uh oh!

chia7712 Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

chia7712 Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

tirthooo7 Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

tirthooo7 commented Feb 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

tirthooo7 commented Feb 3, 2026 •

edited

Loading

`vagrant/base.sh`

Available JDKs in `s3://kafka-packages/jdk/`