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

Utility to migrate through installed version application upgrades #47

Closed
nfx opened this issue Feb 21, 2024 · 1 comment
Closed

Utility to migrate through installed version application upgrades #47

nfx opened this issue Feb 21, 2024 · 1 comment

Comments

@nfx
Copy link
Collaborator

nfx commented Feb 21, 2024

Sometimes, upgrading an installation requires changes not only to config format, but also application state in the form of data assets and workspace assets, like cluster policies, cluster or dashboard configurations, which results in outages while rolling new versions out.

We need:

  • in-wheel package name to iterate over submodules
  • every submodule to be named as v0.12.5.py (verify if this works)
  • every submodule providing upgrade(WorkspaceClient) function to deploy this version upgrade
  • current app version determined from ~/.app/version.json file created by the WheelsV2.upload() method
  • figure out if we execute version migrations atomically or just rely on a version diff and have the upgrader code be resilient to re-applies, possibly via exception ignores and multiple files per release
@nfx
Copy link
Collaborator Author

nfx commented Mar 9, 2024

Fixed in #50

@nfx nfx closed this as completed Mar 9, 2024
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