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 upgrade migration routine for settings #670

Closed
1 task done
dkotter opened this issue Jan 31, 2024 · 0 comments · Fixed by #711
Closed
1 task done

Add upgrade migration routine for settings #670

dkotter opened this issue Jan 31, 2024 · 0 comments · Fixed by #711
Assignees
Milestone

Comments

@dkotter
Copy link
Collaborator

dkotter commented Jan 31, 2024

Is your enhancement related to a problem? Please describe.

Coming out of the large refactoring work done in #611, some changes were made to how settings are saved.

I believe all settings are now stored under new meta keys and any Provider specific settings (like API keys) are now stored under a new array key within those settings.

What this means is that any current ClassifAI users, when they upgrade to the v3 release, all of their settings will be lost. Ideally we should add an upgrade routine that migrates all existing settings into the new structure and probably delete the old settings once done.

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@dkotter dkotter added this to the 3.0.0 milestone Jan 31, 2024
@jeffpaul jeffpaul moved this from Incoming to To Do in Open Source Practice Feb 1, 2024
@Sidsector9 Sidsector9 moved this from To Do to In Progress in Open Source Practice Feb 4, 2024
@jeffpaul jeffpaul moved this from In Progress to In Review in Open Source Practice Feb 12, 2024
@github-project-automation github-project-automation bot moved this from In Review to Merged in Open Source Practice Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants