Skip to content

Script to package up Kafka Connect connector for submission to Confluent Marketplace (neé Confluent Hub)#15113

Closed
rmoff wants to merge 4 commits intoapache:mainfrom
rmoff:confluent-hub-packager
Closed

Script to package up Kafka Connect connector for submission to Confluent Marketplace (neé Confluent Hub)#15113
rmoff wants to merge 4 commits intoapache:mainfrom
rmoff:confluent-hub-packager

Conversation

@rmoff
Copy link
Contributor

@rmoff rmoff commented Jan 22, 2026

Background

There is currently no prebuilt Iceberg connector for Kafka Connect provided with Iceberg. This can make it more difficult than necessary for users who just want to build pipelines, not run gradle :)

Confluent Marketplace (previously "Confluent Hub") is a long-established platform for the distribution of connectors for Kafka Connect, both open-source and proprietary.
At the moment the 1.9.2 version of the connector has been uploaded to the site by Confluent staff as an ad-hoc process.

There are several existing issues from the community regarding: #10745 #14986 #12516

This PR

This PR adds a script to build and package the Iceberg connector for Kafka Connect into the required format for submission to Confluent for inclusion on the Marketplace.

My suggestion would be that as part of the Iceberg release process, release managers use this script and submit the generated archive to Confluent (confluent-hub@confluent.io).
Confluent can then verify the authenticity of the submission by checking the detached GPG signature against the Iceberg KEYS file hosted on apache.org.

Mailing list thread: https://lists.apache.org/thread/fc0dhqtv8717zbw01xvsc7sm203sohpd

@rmoff rmoff marked this pull request as ready for review January 22, 2026 17:19
@nastra nastra requested a review from bryanck January 23, 2026 10:31
@@ -0,0 +1,106 @@
#!/usr/bin/env bash
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering if this should be placed in the dev folder where other build scripts lives. release manager usually runs the script of the root of the project as dev/some.sh . Also might be easier to discover.

not sure what others think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, moved 35483df

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little confused because it looks like we have two copies now. I not sure if this is something we want in the dev folder though. I'm not clear on the timing of this, but I don't think this is something you would run as part of building the release, but rather after the vote succeeded.

Do we intend to publish RCs?

@github-actions github-actions bot added the INFRA label Jan 29, 2026
@rmoff rmoff requested a review from stevenzwu January 29, 2026 16:57

# Add README
cat > "${PKG}/doc/README.md" << EOF
# Apache Iceberg Sink Connector
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor note here, I'm not sure we can get away with not including the Apache License header here. Theoretically this is now a file we are distributing so I think it needs the full header like our normal github readme has.

Copy link
Contributor Author

@rmoff rmoff Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, done db1c6a6


License: Apache License 2.0
EOF

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same license comment here

Copy link
Contributor Author

@rmoff rmoff Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, done db1c6a6

@danielcweeks
Copy link
Contributor

I'm a little confused on the order of how this would be published. We seem to have git commands as part of the publish, but the released artifacts shouldn't depend on the repo, but rather artifacts that have been released and verified.

@rmoff
Copy link
Contributor Author

rmoff commented Feb 2, 2026

I've reworked this into #15212

@rmoff rmoff closed this Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants