What the deployment service will do once compose.yaml has been changed?

[intaniger]

Currently the deployment service will apply the old configuration even the project's compose file has been changed. which will resulted in a hard-to-investigate bug. so we will need to design a behavior of a deployment service carefully before rolling out.

Proposed solutions:

1. panic, require manual intervention to restart a service again.
2. reload a new configuration, but need to be careful with internal state of the deployment service that need to be in-sync.