Importing an integration when the integration pod already exists behaves weirdly

I came to this when going through the documentation about changing the DB PV capacity setting.

If you have a running environment with integrations and you want to change the PV capacity, you need to undeploy syndesis and deploy it with a higher capacity. So you export all the integrations and do oc delete syndesis app - this will remove the syndesis installation but keeps the integrations running.

You deploy a new syndesis CR with higher PV capacity and there are no data - that is obvious because of the change of the PV. So you import the integrations back - by default they are imported in "stopped" state. You go to edit and let's say you want to change something, so you change it and hit "publish". The integration is immediately published and there is no build, so you end up with the old integration still running and if you want to see the changes, you need to re-publish the integration once again.

It's a weird behavior but the scenario is also a bit weird, so feel free to close the issue if you think it doesn't make any sense.