-
Notifications
You must be signed in to change notification settings - Fork 219
feat: make workflow computable without instantiating dependents #1647
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
Conversation
91d8d44
to
fac0211
Compare
Replaces #1641. |
Do we still need the |
Unless you have a way to remove it, yes, we still need it as it's still used in the code. |
...io/javaoperatorsdk/operator/api/config/dependent/DependentResourceConfigurationResolver.java
Show resolved
Hide resolved
...hema/src/main/java/io/javaoperatorsdk/operator/sample/dependent/SchemaDependentResource.java
Show resolved
Hide resolved
Just added 2 remarks, 1 is just conceptuial idea, otherwise makes sense, I like the changes :) |
a24ae1d
to
a6ffa83
Compare
...n/java/io/javaoperatorsdk/operator/processing/dependent/workflow/DefaultManagedWorkflow.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This allows for workflows to be computed at build time, only to be resolved (i.e. associating workflow nodes to actual dependent resources) when needed. In the process, the configuration mechanism of managed dependent resource has been improved to make it possible to resolve the configuration solely from the dependent resource class instead of previously requiring the dependent to be instantiated. This is now done viw the DependentResourceConfigurationResolver class.
a6ffa83
to
0e1bd3f
Compare
Kudos, SonarCloud Quality Gate passed! |
…es (#1647) This allows for workflows to be computed at build time, only to be resolved (i.e. associating workflow nodes to actual dependent resources) when needed. In the process, the configuration mechanism of managed dependent resource has been improved to make it possible to resolve the configuration solely from the dependent resource class instead of previously requiring the dependent to be instantiated. This is now done viw the DependentResourceConfigurationResolver class.
Depends on #1648