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 is one action for the service binding operator that does this : "The availability or the waiting status should be reflected by the related status -> conditions block.". It could be adapted by renaming the "IntegrationConditionServiceBindingsCollectionReady" to something more generic to be reused by other traits.
Before this, the flow of the integration.Status.Phases was controlled by Actions. It seems that traits have a need to do so as well
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
Top level resources such as Integration, IntegrationKit and KameletBinding should wait for the the resources they depends on. As example:
The availability or the waiting status should be reflected by the related
status -> conditions
block.The text was updated successfully, but these errors were encountered: