b-f-chan
commented
3 years ago The original problem statement is not entirely accurate. The script does not automatically upgrade each time.
It first checks if a config file exists and if so, to avoid compatibility issues, will only download the version specified in the config.yaml file. If this file doesn't exist, only then will it grab the latest.
So there is no forced upgrade on each run. Closing this ticket for now until we figure out our upgrade process.
The DMS script currently tries to automatically upgrade to the latest version each time it runs. This was included for ease of testing in a local environment. However, this is not suitable for production.
Users need to have the option & being to choose when / if to upgrade. Forcing the upgrade can cause breaking changes if they need to re-run the DMS for any reason (config changes, re-deploy, etc). This can cause conflicts with what is already running on the cluster.
Remove the automatic upgrade behaviour for now, and we will separately spec out a proper upgrade process.