Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add erase_old_module_code function to do just that during upgrade #85

Open
pbchase opened this issue Aug 1, 2023 · 1 comment
Open

Comments

@pbchase
Copy link
Contributor

pbchase commented Aug 1, 2023

Add function, erase_old_module_code, to
upgrade.py to erase old module versions from a target directory.

Call this new function with a target directory of env.upload_target_backup_dir

@pbchase
Copy link
Contributor Author

pbchase commented Aug 1, 2023

@ChemiKyle @tlstoffs can we safely do this by erasing all but the latest version? Such a plan is a bit ham-handed, but it is easy. The question is, do we need to support the presence of module code that is more modern than the activated version?

If not, we will need to read the activated versions from the database to know when to preserve an older version. I want to be lazy, but I fear we need to "do the right thing"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant