mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 5
774ff8c2d2
Three conflicts, all from main sizing memory parameters off the container limit while this branch moved container environments into one file per role. plugins/filter/memory_filters.py and its test are deleted on main, replaced by the service_memory_mb lookup. This branch only renamed the filter out of its get_ prefix and fixed the docstrings' reStructuredText, so nothing of substance is lost; the deletion is taken. Verified first that no consumer survives: jvm_max_mb, jvm_min_mb and redis_maxmemory_mb appear nowhere in roles/, group_vars/, tests/, plugins/, cli/ or utils/ once the merged tree is in place. web-app-zammad's search service is the only real conflict.37e80b957emoved discovery.type, xpack.security.enabled and ES_JAVA_OPTS from the compose template into templates/env.j2, where an inline `environment:` block is what the compose-environment-from-env-file lint rejects;a7db89ac0bchanged the heap from a literal 512m to half the container's limit. Both intents hold, so the keys stay in env.j2 and the heap now reads ZAMMAD_SEARCH_HEAP_MB, which the merged vars/main.yml already defines through the new lookup. web-app-magento and web-app-shopware keep their inline environment blocks: both carry an explicit nocheck naming the reason, that their single env.j2 is shared with containers the search daemon's keys must not reach. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>