claudiomaradonna/castrum
1
0
Fork 0
Code Issues Pull requests Activity

refactor(playbooks)!: rename handbook to fortify #36

Merged
claudiomaradonna merged 1 commit from refactor/fortify-playbook into main 2026-10-08 14:37:57 +02:00
Conversation 0 Commits 1 Files changed 26 +59 -59
motoko commented 2026-10-08 14:34:03 +02:00
Collaborator
Copy link

Why

The root playbook that applies hardening, the service roles, the
firewall and the sysadmin roles was handbook.yml, a name left from the
project's start that says nothing about what running it does.
fortify.yml says it in the project's own image: a Roman camp was
fortified to the same plan wherever the legion stopped.

What changed

  • handbook.yml is now fortify.yml, and its plays are "Fortify the
    target" and "Fortify the target (Windows)", after os-update.yml's
    "Update OS of the target".
  • Every reference in the docs, the role READMEs, the Makefile's
    PLAYBOOKS and the gates follows the new name.
  • Breaking: run ansible-playbook fortify.yml where
    ansible-playbook handbook.yml was run; handbook.yml is gone.

Verification

  • make check: green, including the syntax check of fortify.yml and
    the tag_selection and play_partition gates that drive it.
  • make test not run (no podman in the agent jail); no molecule
    scenario references the playbook.
## Why The root playbook that applies hardening, the service roles, the firewall and the sysadmin roles was `handbook.yml`, a name left from the project's start that says nothing about what running it does. `fortify.yml` says it in the project's own image: a Roman camp was fortified to the same plan wherever the legion stopped. ## What changed - `handbook.yml` is now `fortify.yml`, and its plays are "Fortify the target" and "Fortify the target (Windows)", after `os-update.yml`'s "Update OS of the target". - Every reference in the docs, the role READMEs, the Makefile's `PLAYBOOKS` and the gates follows the new name. - **Breaking:** run `ansible-playbook fortify.yml` where `ansible-playbook handbook.yml` was run; `handbook.yml` is gone. ## Verification - `make check`: green, including the syntax check of `fortify.yml` and the `tag_selection` and `play_partition` gates that drive it. - `make test` not run (no podman in the agent jail); no molecule scenario references the playbook. 
The root playbook that applies hardening, the service roles, the
firewall and the sysadmin roles was handbook.yml, a name left from the
project's start that says nothing about what running it does.
fortify.yml says it in the project's own image: a Roman camp was
fortified to the same plan wherever the legion stopped.

Its plays are now "Fortify the target" and "Fortify the target
(Windows)", after os-update.yml's "Update OS of the target". Every
reference in the docs, the role READMEs, the Makefile and the gates
follows the new name.

BREAKING CHANGE: run `ansible-playbook fortify.yml` where
`ansible-playbook handbook.yml` was run; handbook.yml is gone.
claudiomaradonna deleted branch refactor/fortify-playbook 2026-10-08 14:38:02 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
claudiomaradonna/castrum!36
No description provided.