You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of version 2.6.0, the new ground truth for these parameters will be the values stored in the new user_settings table.
We cannot drop the user-table columns in 2.6.0, because the version update will need to also update data, as in:
Update fractal-server version to 2.6.0
Run set-db script, which applies schema migrations (and creates user-settings table)
Run update-db-data script, which creates settings for each user (and fills them with current values - where applicable)
You are now in a state where you could run a job, and it would use the new user-settings values. In this same state, the API for viewing/changing user settings is already in place, while the API for the old user attributes is already gone.
Update fractal-server version to 2.6.1 (note: we expect this to take place right away, during the same maintenance session)
tcompa
changed the title
Deprecate use of user slurm_user, cache_dir and slurm_accounts
Deprecate use of user's slurm_user, cache_dir and slurm_accountsSep 19, 2024
As part of version 2.6.0, the new ground truth for these parameters will be the values stored in the new
user_settings
table.We cannot drop the user-table columns in 2.6.0, because the version update will need to also update data, as in:
set-db
script, which applies schema migrations (and creates user-settings table)update-db-data
script, which creates settings for each user (and fills them with current values - where applicable)set-db
script, which removes old columns from user table (and also implements MakeUserOAuth.user_settings_id
required #1781)The current issue, like #1781, will be implemented and merged for 2.6.1
The text was updated successfully, but these errors were encountered: