files_properties
Maintains the ansible/roles/files_properties Ansible role that sets ownership/mode/other file-module properties on existing paths via ansible.builtin.file, as part of the Linux SOE. Use when checking
SKILL.md.claude/skills/files_properties/SKILL.md
GitHubfiles_properties
Maintains ansible/roles/files_properties/. See docs/ARCHITECTURE.md for the shared
conventions (role layout, audit vs. remediate via --check --diff, safety
rules, branch + PR contribution workflow).
ansible/roles/files_properties/README.md documents this role's full
configuration surface (every defaults/main.yml variable, with its
original inline comments, rendered as a single reference). Read it
before proposing or explaining how to configure this role — it
reflects the role's actual current defaults even if a variable summary
elsewhere in this file has drifted out of sync with the role.
Policy & workload awareness
docs/VERTICAL_POLICY.md, docs/HORIZONTAL_POLICY and docs/WORKLOAD.md capture org-wide policy items and
the workloads this SOE actually hosts — either can gain a new or changed
item that this role should reflect. Before auditing, remediating, or
proposing a change, check whether either doc has changed more recently
than this role's own code:
git log -1 --format='%cI %h %s' -- docs/VERTICAL_POLICY.md docs/HORIZONTAL_POLICY.md docs/WORKLOAD.md
git log -1 --format='%cI %h %s' -- ansible/roles/files_properties/
If the docs' latest commit is newer than the role's, this role hasn't been re-assessed against current policy/workload — read both files and judge whether anything added or changed since is relevant to this domain:
- Relevant — propose a concrete change on a branch
(
soe/files_properties/policy-<short-desc>orsoe/files_properties/workload-<short-desc>), same branch + PR workflow as any other role change (see "What to do" above anddocs/ARCHITECTURE.md's "Contribution workflow"). Don't wait to be asked. - Not relevant — say so explicitly (e.g. "checked against
docs/VERTICAL_POLICY.md,docs/HORIZONTAL_POLICYanddocs/WORKLOAD.mdas of<date>, nothing affecting this domain") rather than silently skipping the check.
This check is informational, not a gate — it runs alongside a normal audit/remediate, never blocks one; surface the staleness note alongside the normal output.
What the role actually does
Encoded in ansible/roles/files_properties/defaults/main.yml:
This is a low-level, list-driven building block used both directly (a host
sets files_properties in group_vars/host_vars) and indirectly (e.g. certificates
includes files_remove internally for its exclusive-mode cleanup). Default
is always an empty list — no-op until something sets it.
- Unlike
files_create, this role only manages properties on paths, not their existence/type. Result registered asproperties_files.
This role is sourced from the myllynen/rhel-ansible-roles import
(see git log -- ansible/roles/files_properties) rather than hand-authored for this
repo. Unlike the original reference domains (e.g. timesync, usbguard_setup),
it applies state declaratively via standard Ansible modules and does not
add its own assert-based drift checks on top — an audit here is exactly
what --check --diff reports from the underlying modules, nothing more.
What to do
This role is not referenced by any playbook in ansible/ right now —
not configure_rhel.yml (not even commented out), not
load_balancer_setup.yml/nfs_client_setup.yml/nfs_server_setup.yml/
update_rhel.yml. There is currently no ansible-playbook command that will
invoke files_properties in this repo. Before running it, either:
- Add it to an existing playbook — most often
ansible/configure_rhel.yml'sroles:list (uncomment-style, with avars:entry forfiles_propertiesset to what's actually needed), if what's wanted is a permanent, repeatable part of the host baseline; or - Write a small ad hoc playbook for the one-off task, same shape as
ansible/load_balancer_setup.yml/ansible/nfs_client_setup.yml(avars:block plus aroles: [files_properties]list), if it's a one-time or host-class-specific job that doesn't belong in the general baseline.
Either way, propose it via the branch + PR workflow below rather than running
an untracked local playbook against a real host. Once wired in, audit/remediate
the same way as any other role — --tags files_properties against whichever playbook now
contains it, --check --diff first:
ansible-playbook ansible/<playbook>.yml --tags files_properties --check --diff # audit
ansible-playbook ansible/<playbook>.yml --tags files_properties # remediate
Propose a change to the role itself: never edit and commit directly. On a
branch named soe/files_properties/<short-desc>, edit ansible/roles/files_properties/, validate
locally (--syntax-check, ansible-lint roles/files_properties/, and
--check --diff against a real/test host if available), then push and open a
PR titled [files_properties] <what changed> with the --check --diff output in the
body. Then stop — a human reviews and merges; see docs/ARCHITECTURE.md's
"Contribution workflow".
Wiring into the SOE
This role has a row in .claude/skills/soe/SKILL.md's domain table, but (see
"What to do" above) is not currently included in any playbook in this repo —
neither the general baseline (ansible/configure_rhel.yml) nor any of the
composite playbooks. This repo no longer uses ansible/site.yml; see
docs/ARCHITECTURE.md.