Use docker exec instead of docker cp to create run script for Kafka native DevService

[xstefank]

This also requires ozangunalp/kafka-native#144 to be pushed to quay.io. cc/ @ozangunalp

With this change I was able to successfully run Kafka native DevService in DevSpaces/Che!

config

quarkus.kafka.devservices.provider=kafka-native

This would really help us to get the Quarkus super-heroes workshop to be doable in DevSpaces (fully online).

cc/ also @danieloh30 since I heard that this was a blocker for you.

[ozangunalp]

@xstefank that string format is hard to follow, but it looks good!

Can we do the same for the redpanda container?

[ozangunalp]

@xstefank also, the change itself doesn't require the kafka-native release right? We can cut it after?

Also you can test with the kafka-native latest-snapshot tag that is built & pushed from the main.

[xstefank]

@ozangunalp redpanda has itself similar issue as we fixed in your kafka-native container (permissions for random UID) so until they fix it in their container, we can't do anything on our side.

Add release, yes, this is just a different way to create run.sh script in container so it shouldn't matter. But I see test failures so probably it does?

[ozangunalp]

KafkaDevServicesDevModeTestCase.sseStream is a failing test, not even flaky apparently. I am looking at it. So it is irrelevant for this change.

[gsmet]

The following might be a little less confusing (untested):

Suggested change

	String.format("echo -e \"%s\" >> %s && chmod 777 %s", cmd, STARTER_SCRIPT, STARTER_SCRIPT));
	String.format("echo -e \"%1$s\" >> %2$s && chmod 777 %2$s", cmd, STARTER_SCRIPT));

[xstefank]

Thanks

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 079b2b7.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.