0.17.4

This page documents the changes in Kannika Armory version 0.17.4.

Changelog 0.17.4

Restore: loosened the editing restrictions for performance and pod settings.
Restore: performance and pod settings, such as parallelism, max producers, the service account, resource requirements, and additional properties, can now also be edited when a restore is paused, interrupted, or failed.
Restore: settings that affect what is restored stay locked once the restore has started.
Console: parallelism and max producers moved to a new Performance section on the Restore Settings tab, with its own save button.
GraphQL: configureRestoreOptions now returns the RESTORE_ALREADY_STARTED problem for a blocked edit, instead of reporting success without saving.
GraphQL: configureRestorePodSettings now returns the RESTORE_ALREADY_STARTED problem for a blocked edit, instead of reporting success without saving.
GraphQL: configureRestoreSource now returns the RESTORE_ALREADY_STARTED problem for a blocked edit, instead of reporting success without saving.
GraphQL: configureRestoreSink now returns the RESTORE_ALREADY_STARTED problem for a blocked edit, instead of reporting success without saving.

Restore: retry transient storage errors during snapshot resolution instead of failing the restore immediately.
Restore: the last restored offset from previous attempts is now reported after a restore resumes, instead of -1 for partitions that were fully restored before the interruption.
Console: a missing or negative last restored offset now renders as ’-’ instead of -1, and the partition progress bar treats it as no progress.