Patch `ci_max_total_yaml_size_bytes` migration to handle integer overflow
Add new ci_max_total_yaml_size_bytes applicatio... (!123129 - merged) • Kasia Misirli • 16.3 introduced the ci_max_total_yaml_size_bytes
application setting, but the configuration of the migration has a possible bug as a result of being dependent on user set values. See @linushstge's comment here for context.
This migration should be update to cap to the 4 byte max integer value to prevent the migration from failing. As this can disrupt our users upgrade paths, we need to backport this to %16.3.
Implementation Plan
-
Implement a cap of 2147483647 in the migration to avoid exceeding the max value size of the Postgres Int field. -
Backport the fix to %16.3
MR for 16.3 branch addressing this issue.
MR for master branch addressing this issue.
Edited by Kasia Misirli