Operator should detect changes on Flow CDRs about openintegrationhub HOT 4 CLOSED

Requires additional investigation:
Idea: there should be flow definition crd. There also additional information should be stored for internals of platform (rabbimq accounts for flows, current state, started/stopped/running)
This additional information should be used to find out changes. To understand that flow should be killed and all related things are deleted.
Options:

1. add some read-only properties in flow definition crd. Need to find out how to protect them from external user
2. add "shadow" crd that is used only by platform internally.

Need also understand how to handle crd removal for both options and trigger cleaning on it.

from openintegrationhub.

Statement copied from discussion in #33 :

#32 is in progress, but It's quite complex task so It will take some time to solve the issue.

from openintegrationhub.

@anton-kotenko as stated with merge of pr #104 this issue as well as #24 #26 and #28 can be moved to "done", right? If yes, I'll put them in the right lane.

from openintegrationhub.

@philecs
You are right. Thank you.

from openintegrationhub.