Folder Config

Any folder inside a host or group directory can have a bois.yml or bois.yaml file to configure how that folder and its contents should be deployed.

This is useful for:

• Overriding the destination path for a whole directory tree
• Setting ownership and permissions for all files in that directory

Example

Imagine you have a udev folder in your host directory that should be deployed to /etc/udev/rules.d:

 📂 hosts/
 └ 📂 artifact/
   └ 📂 udev/
     │ bois.yml
     │ 10-network.rules
     └ 20-usb.rules

The bois.yml might look like this:

# Deploy to an absolute path outside the default target directory
path: /etc/udev/rules.d

# Set ownership and permissions
owner: root
group: root
mode: 0o755

Now all files inside the udev folder will be deployed to /etc/udev/rules.d with the specified ownership and permissions.

Configuration Options

• path: PathBuf (optional) - Override the destination path for this directory and all its contents.
  • If it’s a relative path, it’s treated as relative to the target directory.
  • If it’s an absolute path, that absolute path is used directly.
  • This override cascades to all child files and directories, unless they specify their own path.
• owner: String (optional) - The directory owner. Defaults to the current user.
• group: String (optional) - The directory’s assigned group. Defaults to the current user’s group.
• mode: OctalInt (optional) - The permissions for this directory (e.g., 0o755). Defaults to 0o755.

Path Inheritance

When a folder has a path override, all files and subdirectories inside inherit that override:

 📂 systemd/
 │ bois.yml (path: /etc/systemd/system)
 ├ 📂 timers/
 │ └ backup.timer
 └ 📁 services/
   └ backup.service

Both timers/backup.timer and services/backup.service will be deployed under /etc/systemd/system/ unless they specify their own path override.