-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify Halkyon runtime and version #389
Comments
Note that in the resource produced by Dekorate, the |
@jponge: This is something that we do support for Spring, but its a little bit hard to be able to tell when the runtime is vert.x. We could possibly scan the classpath for known vert.x classes and from there we could pick up the version too. |
The issue here is that the project version clashes with the runtime version. You could indeed scan the classpath for the presence of |
Even though Quarkus does use dekorate, this is done usually via the quarkus kubernetes extension, so its pretty clear when we are talking about quarkus or not. |
For JKube (the new fabric8 maven plugin replacement) here is the generator used to determine if a project is a Vert.x project: |
I have been able to deploy a Vert.x component with the following hand-crafted resource:
Now I would like to have fun with
hal
and Dekorate, so I have this (annotation-less) file:which generates the following
target/classes/META-INF/dekorate/halkyon.yml
:It is missing runtime info, causing Halkyon to fail, and I cannot specify this with Dekorate.
The text was updated successfully, but these errors were encountered: