Alex Soto
Sure thank you so much. Probably not something I could do right now but in the near future.
@iocanel One question, does this issue implies jut creating `configmap` https://kubernetes.io/docs/tasks/configure-pod-container/configmap/ from Cube right?
Or like we are doing in docker compose format. Ok I ll work on it El 8 may. 2017 8:44 p. m., "Ioannis Canellos" escribió: > my understanding is that...
@jwendell The question is, currently if you do not do anything Cube creates a new random `itest` namespace created by test suite execution. So what you are saying here is...
Yes, the container is materialized at testenricher phase which is before test phase. I am not aware how exactly this works with Test NG, but as I said the container...
Look can you try to put a debug point at https://github.com/arquillian/arquillian-cube/blob/master/docker/docker/src/main/java/org/arquillian/cube/docker/impl/client/containerobject/CubeContainerObjectTestEnricher.java#L103 and see exactly in which phase is run in Test NG?
One comment, now I see that you've moved from BuildablePod logic to template logic, doesn't this mean that this logic is only executed in case of templates where before was...
This is what I don't know, but it seems to me (I am not deeply familiar with this piece) that we are moving the functionality instead of fixing in one...
no idea in this part
Seems good to me, @iocanel or @jwendell can you take a quick review before I merge it? Thank you very much.