Okey, then, we should be done. Right now I'm reorganizing docs between the
different repos as well, moving the Kamelets part into the Kamelet Catalog
repo, but I think we can manage as a separate PRs.
>From next release (4.9) onward we will need to communicate the CRD spec and
the java CRD depende
Thanks Pasquale,
I personally think everything related to Kamelets should be on Camel-Kamelets
repository.
So I would move it there.
Are there any relationship with the website and the CRDs? Do we need to modify
something in terms of docs?
Thanks.
--Andrea Cosentino -
Hello again.
Since we did not yet reach an agreement on where to have the CRD spec, I've
made a draft PR to show what exactly is the code we'll be required to
manage [1]. We can decide to keep it where it is, on Kamelets catalog
project or either move to Camel or a brand new subproject. If we keep
Hello,
replies inline.
On Tue, Sep 10, 2024 at 9:14 AM Christoph Deppisch
wrote:
> > 1. Move the spec into another separate project
> I think you wrote that the Java CRD model is not part of this new
> sub-project. Why is this? Can't we just also have this as a Java artifact
> as part of the sub
Thanks Christoph.
>From Camel K perspective there won't be any "logical" problem. In the sense
that it will copy the specification from the new source when it has to
bundle the Kamelets CRDs. As the API versioning model is different from the
typical semantic versioning I don't expect big issues wh
Hello Pasquale,
+1 on moving the Java CRD model generation as it is a source of circular
dependencies. But what about the pure CRD YAML definitions (
https://github.com/apache/camel-k/tree/main/pkg/resources/config/crd/bases)?
>From a Camel K operator perspective wouldn't it be weird to loose the
Thanks Andrea,
yes, there will be quite some work to do as we have many circular
references and other aspects which we need to move off from Camel K. The
CRDs project should be partially moved as well, as it contains the
dependency used by the tooling. Fortunately Kamelets should not have
reference
Hello Pasquale,
I think it makes sense.
This will mean moving the following project and the related crds in base,
right?
https://github.com/apache/camel-k/tree/main/java/crds
Il giorno lun 2 set 2024 alle ore 17:18 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:
> Hi folks,
>
Hi folks,
in the past we've discussed the opportunity to move the specification of
Kamelet from Camel K to Camel since Kamelets have been a general concept
for some time. I'd like to set the ground for a shared decision on what to
achieve. I will create a JIRA, but, before, I'd like to understand i
