Problem

Cannot perform a rolling deployment if the SSH key changes, e.g., when the configuration is applied from different machines or by different users.

> dstack apply -f my-service.dstack.yml                        

Active run test-service already exists. Detected changes that cannot be updated in-place:
- Public SSH key

Stop and override the run? [y/n]:

Solution

Support rolling deployments when SSH key changes.

Workaround

Use dstack apply --ssh-identity ... so that the key is always the same.

Would you like to help us implement this feature by sending a PR?

Yes