Registry phase 2 migration: Database/model changes
Context
The context for this issue can be viewed in the epic &7316 (closed) and the breakdown of work can be viewed in this comment &7316 (comment 792633854).
Database changes
New columns for application_settings
- these settings will be adjusted over time as we slowly make our way through importing all of the container repositories:
-
container_registry_max_tags_count
- The maximum number of tags we will allow a container repository to have to qualify for import. -
container_registry_import_max_retries
- The number of import retries to try before skipping the import. -
container_registry_import_start_max_retries
- The number of retries to enqueue the import before skipping. -
container_registry_import_max_step_duration
- Consider aborting or skipping the import if it is taking longer than this value. -
container_registry_import_target_plan
- The plan to import from (we are starting with 'free'). -
container_registry_import_created_before
- Container repositories created before this date will qualify for import (end of 14.7, or before 2022-01-23).
New columns for container_repositories
:
-
migration_state
- The current import state of the container repository. -
migration_pre_import_started_at
- When the pre-import process started. -
migration_pre_import_done_at
- When the pre-import process finished. -
migration_import_started_at
- When the import process started. -
migration_import_done_at
- When the import process finished. -
migration_skipped_reason
- Reason why the container repository import may have been skipped. -
migration_skipped_at
- When the import was skipped. -
migration_aborted_in_state
- Whatmigration_state
the container repository was in when it was aborted. -
migration_retries_count
- Number of retries for the container repository.
Edited by Steve Abrams