Salva Alcántara

@suhothayan What is the current state? Could you please share your thoughts on how to deal with this issue?

Hey, what is the current state of this issue?

Hi @ariskk, thanks for your replies. I've got some more questions regarding the scope of this library: - As you say, I guess the idea here is to cover everything...

BTW @ariskk `flink-type-info` seems to have disappeared (???), but there is the magnolia-based equivalent: https://github.com/findify/flink-adt, which I guess would play the same role.

Hey @ariskk, have you seen this: https://github.com/findify/flink-scala-api? It clearly overlaps with this project and seems way more advanced. I came across this here: https://lists.apache.org/thread/3ghw0cvkftv349j9x4j3h1twzwt75fwj.

@ariskk I think it would make more sense to unite forces in `flink-scala-api` (and `flink-adt`). Wouldn't it be possible to add whatever extensions on top of `flink-scala-api`, which already covers...

@ariskk Another thing I noticed is that you use case classes for everything (e.g., `DataStream`) while the official `flink-scala` (as well as `flink-scala-api`) uses regular classes. Using case classes might...

FYI @dhiguero, I opened [this issue](https://github.com/kubevela/catalog/issues/747) to target the `fluxcd` addon specifically first. Issues are cross-referenced now.

The version was bumped at some point but the same issue happens again: ``` url: "https://downloads.apache.org/flink/flink-kubernetes-operator-1.3.1/" chart: "flink-kubernetes-operator" version: "1.3.1" ``` For what it's worth version `1.3.1` does no longer...

On a related note, I've observed that for each component of type `helm` in my application, I get both a `HelmRepository` and a `HelmRelease` being created. In the described scenario...