Skip to content
Install

Decision records

The decisions that shape what Volant users see, and why they were taken.

A decision record explains one choice that affects Volant’s users: what the situation was, what was decided, and what follows from it. The records use the MADR format and are numbered in the order they were taken.

A record is not rewritten once it is accepted. When a later decision changes it, the status line says so and links to the new record. Measurements taken after the decision are added as dated sections at the end.

Record Decision
0001 License the repository under GPL-3.0-or-later. Interface crates are the exception, see 0009.
0002 Reproduce ansible-core 2.19, and treat any difference as a bug.
0003 ansible_version reports the reference release; volant_version reports Volant’s.
0004 become starts a second agent under sudo.
0005 A host keeps its fork permit across host-local steps, behind the batching option.
0006 Send one union blob of Python modules per run, and fork them from a warm server.
0007 Run action plugins as a sequence of sub-tasks driven by the controller.
0008 Answer common modules natively in the agent, hand the rest to Python, and share one ssh connection per host.
0009 Keep the engine under GPL-3.0-or-later, and license crates that describe a public interface MIT OR Apache-2.0.
0010 Let a project choose the ansible-core release Volant reproduces (2.19 or latest), keep what Ansible removed with a warning, and list what an upgrade changes (volant upgrade-plan).
0011 Extend Ansible only through keys a command can lower back to plain Ansible (volant eject, volant check --portable).
0012 volant galaxy fetches over HTTP in process (ureq, rustls, the system CA store) and unpacks with the tar and flate2 crates; git and gpg stay external.