Extensions and the Java generator

[andreaTP]

Since version 6 of this project, we started shipping a java-generator capable of automatically producing the Java implementation of arbitrary CRDs.

Switching the current "extensions" to the java-generated version of them is definitely possible from the functional side:

kubernetes-client/java-generator/it/src/it/extensions/src/test/java/io/fabric8/it/extensions/camelk/JavaGeneratedCamelK.java

Lines 31 to 72 in 962de1d

	public static CamelCatalog dummyCamelKCatalog() {
	CamelCatalog camelCatalog = new CamelCatalogBuilder()
	.withNewMetadata()
	.withName("dummy")
	.endMetadata()
	.withNewSpec()
	.addToArtifacts("artifact1",
	new ArtifactsBuilder()
	.withArtifactId("artifact1ID")
	.withDataformats("dataformat1")
	.withDependencies(
	new org.apache.camel.v1.camelcatalogspec.artifacts.DependenciesBuilder()
	.withArtifactId("artifact2")
	.withGroupId("mygroupid")
	.withVersion("1.0.0")
	.withExclusions(
	new ExclusionsBuilder()
	.withArtifactId("artifact3")
	.build()
	)
	.build()
	)
	.withGroupId("mygroupid")
	.withJavaTypes("javatype1", "javatype2")
	.withLanguages("java", "kotlin")
	.build()
	)
	.withRuntime(
	new RuntimeBuilder()
	.withVersion("2.0.0")
	.withProvider("myprovider")
	.withDependencies(
	new org.apache.camel.v1.camelcatalogspec.runtime.DependenciesBuilder()
	.withArtifactId("aid")
	.withGroupId("gid")
	.withVersion("v")
	.build()
	)
	.build()
	)
	.endSpec()
	.build();

kubernetes-client/java-generator/it/src/main/java/io/fabric8/java/generator/testing/extensions/camlek/ExtensionCamelK.java

Lines 27 to 62 in 962de1d

	public static CamelCatalog dummyCamelKCatalog() {
	CamelCatalog camelkCatalog = new CamelCatalogBuilder()
	.withNewMetadata()
	.withName("dummy")
	.endMetadata()
	.withNewSpec()
	.addToArtifacts("artifact1",
	new CamelArtifactBuilder()
	.withArtifactId("artifact1ID")
	.withDataformats("dataformat1")
	.withDependencies(
	new CamelArtifactDependencyBuilder()
	.withArtifactId("artifact2")
	.withGroupId("mygroupid")
	.withVersion("1.0.0")
	.withExclusions(
	new CamelArtifactExclusionBuilder()
	.withArtifactId("artifact3")
	.build())
	.build())
	.withGroupId("mygroupid")
	.withJavaTypes("javatype1", "javatype2")
	.withLanguages("java", "kotlin")
	.build())
	.withNewRuntime()
	.withVersion("2.0.0")
	.withProvider("myprovider")
	.withDependencies(
	new MavenArtifactBuilder()
	.withArtifactId("aid")
	.withGroupId("gid")
	.withVersion("v")
	.build())
	.endRuntime()
	.endSpec()
	.build();

The current "extensions" are hard to maintain and they do require resources and constant attention, it would be nice to switch to the generated version, but the result is going to be API incompatible (on the Java side) therefore there is no straightforward path.

Here I'm asking for community feedback on this possible switch and how it can be performed to reduce user disruption.

We have been thinking about a few ideas:

• start to publish the "generated" version of one of the current "extension"
• publish the generated code from an external repository for multiple CRDs