This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 202
Configuration syntax #15
Comments
Oops, duplicate of #18 |
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Jan 8, 2018
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Jan 16, 2018
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Jan 16, 2018
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Jan 17, 2018
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Jan 21, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current the configuration is quite simplistic, reusing
<build>
from the docker configuration and the portmapping from<run>
.Especially the latter probably doesnt make much sense.
Also the question is, whether annotation and label configuration should be done in more nested way. Also, label config is currently global for all objects (as in v2) but could be more fine granular and different for RC, Pods, Services ....
The profile
new
in the cdi-sample is are some first thoughts about a possible structure. Need still a night :)The text was updated successfully, but these errors were encountered: