From b11a596fc9a8f4cd284dfc0dc5bb8f2279f9694e Mon Sep 17 00:00:00 2001 From: Maksim Rusan Date: Wed, 11 Dec 2024 16:39:17 +0100 Subject: [PATCH] chore(armory): Update title and fix typo --- kb/armory/General/db-compression-rollback.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kb/armory/General/db-compression-rollback.md b/kb/armory/General/db-compression-rollback.md index 653c848a6a..9c08b701e5 100644 --- a/kb/armory/General/db-compression-rollback.md +++ b/kb/armory/General/db-compression-rollback.md @@ -1,5 +1,5 @@ --- -title: Execution repository compression rollback +title: Execution Repository Compression Rollback for Downgrades to Versions Incompatible with Compression --- ## Problem Description @@ -7,7 +7,7 @@ title: Execution repository compression rollback [Spinnaker Orca Pull Request #4620](https://github.com/spinnaker/orca/pull/4620) introduced improvements for handling large payloads by storing compressed bodies in the database. Unfortunately, in the case of a rollback to a version which does not support compression - Spinnaker will fail to render executions, because the `body` would effectively be -empty, as it would be store in a corresponding entry as `compressed_body` in a table with `_compressed_executions` +empty, as it would be stored in a corresponding entry as `compressed_body` in a table with `_compressed_executions` appended. ## Workaround