allow pod templates to be combined? about fabric8-maven-plugin HOT 5 CLOSED

I guess this example shows how we can use the builder stuff to add custom containers:
https://github.com/jstrachan/fabric8-devops/blob/0de82b3b04b0b3c2d4c89b1668e1e9d795bc8c48/kibana/src/main/java/io/fabric8/apps/kibana/KibanaModelProcessor.java#L36-L36

we'd just need a way to load (maybe inject?) an RC via maven coordinates?

from fabric8-maven-plugin.

Do you mean to extract the pod template from the infinispan server RC.yaml and include it into the list of containers for the app to create ?

If it is only about adding containers from other images (whose build is not managed by the pom.xml) to the set of containers for a pod, then this should be easily possible with the new configuration structure.

Since we include d-m-p which knows how to deal with multiple images in its configuration (originally intended for doing plain docker integration tests where other images needs to be started as deps), this can be added easily.

Currently I'm fiddling with the configuration syntax, will have a proposal and the end of the day.

Next steps is then to pick up external config files which can be 'enriched' like in https://github.com/fabric8io/fabric8-maven-plugin/blob/master/src/main/java/io/fabric8/maven/fabric8/enricher/impl/ProjectInfoEnricher.java

from fabric8-maven-plugin.

@rhuss yes thats exactly what I mean - being able to reuse in some app the container from a separate project's RC as a sidecar

from fabric8-maven-plugin.

another use case off the top of my head - being able to co-locate the APIman proxy gateway; or the fabric8 messaging gateway as a sidecar container in a pod. i.e. reuse a container from a separate maven project's RC.yml

from fabric8-maven-plugin.

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

from fabric8-maven-plugin.