You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are cases where whether or not a resource needs to be created / updated / deleted, depends on the content of the primary (or even secondary) resource(s). This isn't currently possible but should be supported. A relatively easy to support this use case would be to introduce isCreatable(P primary, Context context) (and associated) methods on AbstractDependentResource so that implementations could provide their own logic if needed.
The text was updated successfully, but these errors were encountered:
IMO this should be covered by Conditions, not decided dynamically.
The current logic is that if a Dependent Resource is marked with Creator, Updater , Deleter interface, the respected operation should be executed. It could be very confusing, if something is marked for example Creator, reconcile() is called but its not created.
There are cases where whether or not a resource needs to be created / updated / deleted, depends on the content of the primary (or even secondary) resource(s). This isn't currently possible but should be supported. A relatively easy to support this use case would be to introduce
isCreatable(P primary, Context context)
(and associated) methods onAbstractDependentResource
so that implementations could provide their own logic if needed.The text was updated successfully, but these errors were encountered: