-
Notifications
You must be signed in to change notification settings - Fork 51
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
Bumping to Quarkus 3.18.x or 3.19.x causes exception of "Couldn't instantiate DependentResource" #1059
Comments
This seems like a bug, indeed. Investigating. Thank you for the report and the information! |
Fixes #1059 Signed-off-by: Chris Laprun <[email protected]>
It should be addressed with #1064. If you get a change to try it out, let me know if it works and I will cut a new release. |
Hey @metacosm Thanks for the quick feedback. Sure I can try it out, is there a snapshot/R.C version artifact published that I can use to test? |
OK, I will merge then so that a snapshot can be deployed. |
The snapshot version can be found at: https://s01.oss.sonatype.org/content/repositories/snapshots/io/quarkiverse/operatorsdk/ |
Hello again @metacosm Yes, it seems to be all good now. Thanks a lot. |
For context, i'm currently running Quarkus 3.17.8 and Kotlin 2.0.21. Also using Quarkus Operator SDK (version defined via the Quarkus Platform).
I have a Reconciler with a DependentResource, and that DependentResource has a dependency that is being injected by Quarkus:
This works and has been working.
Now when upgrading to Quarkus 3.18.x or even 3.19.x (for simplification I'm using 3.19.1), I have done all the needed changes for JOSDK v5 (in the example above, use the
@Workflow
annotation to declare a dependent resource for example) and it is failing to start with:Thanks in advance.
The text was updated successfully, but these errors were encountered: