Make it possible to define the container image without IntegrationKit

[lburgazzoli]

Release Note

NONE

[astefanutti]

Thinking out loud, I wonder whether we could skip the creation of the kit altogether, by setting the Integration .status.image field directly from the new container trait configuration parameter? I find creating an empty IntegrationKit rather useless, even misleading.

[lburgazzoli]

Thinking out loud, I wonder whether we could skip the creation of the kit altogether, by setting the Integration .status.image field directly from the new container trait configuration parameter? I find creating an empty IntegrationKit rather useless, even misleading.

Yep, that would be an option however I wasn't sure if the IntegrationKit is maybe referenced somewhere in the processing pipeline

[lburgazzoli]

@astefanutti so yes, at the moment the IntegrationKit is likely needed as the environment requires it and some of the trait expect it to be defined i.e. to borrow configurations & so on so we may need a deep refactor if we want to have an option to entirely skip it.

[astefanutti]

@astefanutti so yes, at the moment the IntegrationKit is likely needed as the environment requires it and some of the trait expect it to be defined i.e. to borrow configurations & so on so we may need a deep refactor if we want to have an option to entirely skip it.

The opposite would have been surprising :) It should be fine to do it in two steps, and implement the kitless approach in a second issue. Even after an upgrade to the later version, the Integration should work seamlessly.

[astefanutti]

Now if we decide to stick to the proposed approach, would enlisting the IntegrationKit into the environment resources, and let the deployer trait apply it work, instead of creating it explicitly?

[lburgazzoli]

@astefanutti so yes, at the moment the IntegrationKit is likely needed as the environment requires it and some of the trait expect it to be defined i.e. to borrow configurations & so on so we may need a deep refactor if we want to have an option to entirely skip it.

The opposite would have been surprising :) It should be fine to do it in two steps, and implement the kitless approach in a second issue. Even after an upgrade to the later version, the Integration should work seamlessly.

We really need to sit down ad rethink a little how traits are implemented, guess there is room for improvement.

[lburgazzoli]

Partial implementation of #2232