mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5
82a5eb83f2
Registering variant_bundle/max_storage in ORDERED_HANDLERS was right - the key had never reached a generated .env - but the handler imported its default from utils.github.variant_bundles, and that module pulls humanfriendly and, through utils.cache.applications, yaml. The .env generator imports every registered handler and has to run on the bare bootstrap python, so one constant import took it down. Move both defaults into a stdlib-only module. This also ends a duplication the handler layer had already been carrying: size.py spelled out '3' while variant_bundles held the same 3 - the very thing max_storage tried to avoid by importing, at the cost of the layer boundary. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
13 lines
441 B
Python
13 lines
441 B
Python
"""Default bundle limits for the CI deploy-matrix discovery.
|
|
|
|
Kept apart from :mod:`utils.github.variant_bundles`, which reaches yaml and
|
|
humanfriendly at import time: the env handlers that seed these defaults are
|
|
imported by the .env generator on the bare bootstrap python, where no
|
|
third-party module exists. This module must stay stdlib-only.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
DEFAULT_BUNDLE_SIZE = 3
|
|
DEFAULT_MAX_STORAGE = "350GB"
|