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
No longer require that "upgrade_storage_uri" is set. This will enable migrations that use non-disk storage in future, but it should be noted that the migration from disk to non-disk (postgresql) storage is a separate step that should only be done after upgrading to 0.14.0 - see issue #1079.
Update kvx to support namespace migrations.
Remove upgrade_storage_uri from Config
Remove all direct file / directory access in upgrade code (use KV instead)
Move data_dir_from_storage_uri to Config (only used for tls_dirs, repo_dir and pid_file)
Move storage_uri_from_data_dir to Config
Use the in-memory data store for automated upgrade tests (make this configurable)
Note: issue #1098 was made to improve version upgrades in clustered setups.
The text was updated successfully, but these errors were encountered:
No longer require that "upgrade_storage_uri" is set. This will enable migrations that use non-disk storage in future, but it should be noted that the migration from disk to non-disk (postgresql) storage is a separate step that should only be done after upgrading to 0.14.0 - see issue #1079.
kvx
to support namespace migrations.Config
data_dir_from_storage_uri
toConfig
(only used fortls_dirs
,repo_dir
andpid_file
)storage_uri_from_data_dir
toConfig
Note: issue #1098 was made to improve version upgrades in clustered setups.
The text was updated successfully, but these errors were encountered: