0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 02:54:26 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5.5 21eba1e88f fix(backup): carry hard links, ACLs and xattrs on every backup and recover hop

baudolo 7.1.x writes volume generations with `rsync -aHAX`, so the
producing host keeps `user.*` extended attributes (OpenCloud keeps its
storage metadata in `user.oc.*`). Every later copy dropped them again,
because none of the other rsync calls passed `-X` (nor `-A`/`-H`):

- NFS export snapshots (svc-bkp-nfs-2-local `script.sh`),
- the backup host's pull (svc-bkp-remote-2-local `pull_specific_host.py`),
- the device sync (svc-bkp-local-2-device `script.py`),
- every recover into a live target (`utils/recovery/base.py`, used by the
  volume, NFS and device recover scripts),
- the `recover full` and `recover remote` tree pulls.

A disaster recovery through the documented chain therefore restored
OpenCloud without `user.oc.*`, silently: the copies succeeded and the
dirval stamp does not cover attributes.

All of these now run `rsync -aHAX` (`-aHAXP` for the device sync). A
target filesystem without xattr support makes rsync exit non-zero as soon
as a source file carries attributes, so the hop fails loudly instead of
dropping them; there is no per-device opt-out. The single-image pull in
`recover remote` keeps `-a`. The provider's ssh-wrapper needs no change:
its glob accepts any server flags and its character guard allows them.

Two tests write a `user.oc.id` attribute and assert it survives the NFS
snapshot and the recover; with the old `-a` both fail with
`OSError: [Errno 61] No data available`.

Closes #1021

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-20 18:20:46 +02:00

annotations

…

cache

perf(cache): let nested lookups reuse the unrendered applications view

2026-10-17 19:52:34 +02:00

claude

…

cleanup

…

diagnostics

fix(diagnostics): let the in-zone probes read the drop-in that holds the zone

2026-09-03 12:50:58 +02:00

docker

fix(images): leave eol roles out of image discovery

2026-10-14 01:19:28 +02:00

domains

…

env

fix(env): reach ip_range through the handler registry

2026-10-19 09:46:18 +02:00

github

feat(ci): compose titles carry the direct arm glyph

2026-10-17 00:03:18 +02:00

handler

fix(vault): keep ansible off the CI runner host's import path

2026-09-08 22:28:47 +02:00

install

fix(lint): provision mmdc's browser libraries off apt and fail hard

2026-10-15 23:45:54 +02:00

inventory

…

mail

fix(swarm-stalwart): fix mailu issue in swarm chunk 1

2026-09-12 21:13:08 +04:00

manager

fix(inventory): stop holding a default's template text to the value's pattern

2026-09-14 22:29:59 +02:00

README.md

Shared Utilities (`utils/`)

This directory contains shared Python helpers used by custom modules and plugins.

Purpose

Use utils/ for reusable code that should not be duplicated across:

library/ modules,
plugins/action/,
plugins/filter/,
plugins/lookup/.

Typical shared utilities:

API clients,
validation/conversion helpers,
path and configuration helpers,
cross-plugin/module domain logic.
Shared HTTP(S) connection handler for multiple modules.
Common validation or transformation functions for user input.
Utility functions for interacting with Docker, LDAP, etc.
Grouped helper packages such as utils/domains/ for related domain logic.

Design Guidelines

Keep helpers focused and composable.
Avoid side effects during import.
Prefer explicit function/class APIs over implicit globals.
Keep dependencies minimal so modules/plugins stay lightweight.

Example Import

from utils.domains.primary_domain import get_primary_domain

What Does Not Belong Here

Standalone executable modules (put in library/).
Ansible plugin entrypoints (put in plugins/*).

References

Module utilities: https://docs.ansible.com/ansible/latest/dev_guide/developing_module_utilities.html
Plugin development: https://docs.ansible.com/ansible/latest/dev_guide/developing_plugins.html