Component CRD spec support ENV vars but not @CompositeAnnotation about dekorate

[iocanel]

The idea is that an annotation processor may reuse config provided by another processor in order to avoid dublicating all configuration all across the board. So in this case we are reusing the KubernetesConfig that was created by the KubertnetesAnnotationProcessor. In the same spirit we are also reusing the configuration provided by the servicecatalog annotation and so on.

So we have the following options here:

Use @CompositeApplication complementary to @KubernetesApplication.

Pros:

• Promotes reusability (more lean approach).

Cons:

• Might not be obvious.

Make @CompositeApplication stand alone, and replicate everything from @KubernetesApplication.

Pros

• simplicity in the design
• possibly easier to understand (?)

Cons

• code dublication.

[cmoulliard]

As a CompositeApplication model (like also K8s or OpenShift) are tightly coupled with their corresponding APIs + version such as by example : Component Api version v1alpha1, then we must find a way to keep this relation, ....

[cmoulliard]

Let's go for the moment to generate CompositeApplication as standalone. @iocanel