mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
meta/schema.yml held credential definitions and their runtime values, but the name said 'schema' and read like structural metadata next to services.yml and volumes.yml. Nothing in the file is a schema in the sense the other meta files use the word, and a contributor had to open it to learn it holds secrets. 62 role files renamed. ROLE_FILE_META_SCHEMA becomes ROLE_FILE_META_SECRETS and keeps its role as the SPOT the path is built from. Two readers bypassed that constant and spelled the name themselves: utils/cache/applications.py built meta_dir / 'schema.yml' twice, and plugins/lookup/application_gid.py carries the filename in the marker list it detects application roles by. Left behind, the rename would not have raised — credentials would have resolved empty and the role would have stopped counting as an application. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
11 lines
364 B
YAML
11 lines
364 B
YAML
---
|
|
credentials:
|
|
administrator_password:
|
|
description: Initial password for the LDAP administrator (e.g. cn=admin,dc=example,dc=com)
|
|
algorithm: sha256
|
|
validation: ^[a-f0-9]{64}$
|
|
administrator_database_password:
|
|
description: Password used internally for the database-backed directory admin
|
|
algorithm: bcrypt
|
|
validation: ^\$2[aby]\$.{56}$
|