ci: install cinc workstation in integration

Signed-off-by: Dan Webb <dan.webb@damacus.io>

Author: damacus

.github/workflows/ci.yml

@@ -42,8 +42,8 @@ jobs:
     steps:
       - name: Check out code
         uses: actions/checkout@v6
-      - name: Install Chef
-        uses: actionshub/chef-install@6.0.0
+      - name: Install Cinc Workstation
+        uses: sous-chefs/.github/.github/actions/install-workstation@6.0.0
       - name: Dokken
         uses: actionshub/test-kitchen@3.0.0
         env:
@@ -57,4 +57,6 @@ jobs:
         run: |
           set -x
           sudo journalctl -l --since today
-          KITCHEN_LOCAL_YAML=kitchen.dokken.yml /usr/bin/kitchen exec ${{ matrix.suite }}-${{ matrix.os }} -c "journalctl -l"
+          if command -v kitchen >/dev/null 2>&1; then
+            KITCHEN_LOCAL_YAML=kitchen.dokken.yml kitchen exec ${{ matrix.suite }}-${{ matrix.os }} -c "journalctl -l"
+          fi

.markdownlint-cli2.yaml

@@ -3,3 +3,8 @@ config:
   line-length: false # MD013
   no-duplicate-heading: false # MD024
   reference-links-images: false # MD052
+  no-multiple-blanks:
+    maximum: 2
+ignores:
+  - .github/copilot-instructions.md
+  - .windsurf/**

LIMITATIONS.md

@@ -4,43 +4,43 @@
 
 ### Upstream / Vendor
 
-- Upstream publishes source tarballs and installation instructions, not an official package repository. The latest published upstream tarball is `djbdns-1.05.tar.gz`.
-- Upstream installation guidance requires a UNIX-like system plus `daemontools` 0.70 or later and `ucspi-tcp`, then a local compile and `make setup check`.
+* Upstream publishes source tarballs and installation instructions, not an official package repository. The latest published upstream tarball is `djbdns-1.05.tar.gz`.
+* Upstream installation guidance requires a UNIX-like system plus `daemontools` 0.70 or later and `ucspi-tcp`, then a local compile and `make setup check`.
 
 ### APT (Debian / Ubuntu)
 
-- Debian still ships `djbdns` as a maintained source package and builds split binaries including `axfrdns`, `djbdns-conf`, `djbdns-utils`, `dnscache`, `rbldns`, `tinydns`, and `walldns`.
-- Debian package pages for current and recent releases show distro-managed package availability for supported Debian architectures.
-- Ubuntu still carries `djbdns` in the `universe` source package set. The cookbook's current package-install path is therefore most defensible on Debian-family platforms.
+* Debian still ships `djbdns` as a maintained source package and builds split binaries including `axfrdns`, `djbdns-conf`, `djbdns-utils`, `dnscache`, `rbldns`, `tinydns`, and `walldns`.
+* Debian package pages for current and recent releases show distro-managed package availability for supported Debian architectures.
+* Ubuntu still carries `djbdns` in the `universe` source package set. The cookbook's current package-install path is therefore most defensible on Debian-family platforms.
 
 ### DNF / YUM (RHEL family)
 
-- I did not find a primary-source upstream package repository for RHEL-family systems.
-- Inference: the cookbook's source-install path remains the only installation path directly backed by upstream documentation for RHEL-family platforms.
+* I did not find a primary-source upstream package repository for RHEL-family systems.
+* Inference: the cookbook's source-install path remains the only installation path directly backed by upstream documentation for RHEL-family platforms.
 
 ### Zypper (SUSE)
 
-- I did not find a primary-source upstream package repository for SUSE/openSUSE.
-- Inference: source installation is also the only path clearly supported by upstream guidance on SUSE-family platforms.
+* I did not find a primary-source upstream package repository for SUSE/openSUSE.
+* Inference: source installation is also the only path clearly supported by upstream guidance on SUSE-family platforms.
 
 ## Architecture Limitations
 
-- Upstream does not publish a tested architecture matrix; its guidance is source-build oriented rather than architecture-specific.
-- Debian and Ubuntu package availability is distribution-managed and architecture-dependent. The cookbook should treat package installs as Debian-family specific, not universally portable.
+* Upstream does not publish a tested architecture matrix; its guidance is source-build oriented rather than architecture-specific.
+* Debian and Ubuntu package availability is distribution-managed and architecture-dependent. The cookbook should treat package installs as Debian-family specific, not universally portable.
 
 ## Source / Compiled Installation
 
 ### Build Dependencies
 
-- Debian: compiler and build tools; upstream also requires `daemontools` and `ucspi-tcp`
-- RHEL: compiler and build tools; upstream also requires `daemontools` and `ucspi-tcp`
-- SUSE: compiler and build tools; upstream also requires `daemontools` and `ucspi-tcp`
+* Debian: compiler and build tools; upstream also requires `daemontools` and `ucspi-tcp`
+* RHEL: compiler and build tools; upstream also requires `daemontools` and `ucspi-tcp`
+* SUSE: compiler and build tools; upstream also requires `daemontools` and `ucspi-tcp`
 
 ## Known Issues
 
-- The cookbook's `install_method` heuristic is cookbook-local logic, not upstream vendor guidance.
-- The cookbook metadata currently advertises platforms that are broader and older than the upstream/package evidence gathered here. Platform modernization should be handled explicitly and separately from this resource migration.
-- `axfrdns` depends on `tcpserver` from `ucspi-tcp`, but the cookbook does not yet model that dependency as a first-class resource concern.
-- Current Dokken integration coverage is still gated by the shared `runit` dependency rather than djbdns resource convergence. In this session:
+* The cookbook's `install_method` heuristic is cookbook-local logic, not upstream vendor guidance.
+* The cookbook metadata currently advertises platforms that are broader and older than the upstream/package evidence gathered here. Platform modernization should be handled explicitly and separately from this resource migration.
+* `axfrdns` depends on `tcpserver` from `ucspi-tcp`, but the cookbook does not yet model that dependency as a first-class resource concern.
+* Current Dokken integration coverage is still gated by the shared `runit` dependency rather than djbdns resource convergence. In this session:
   Debian 12 failed because `runit::default` installs `runit-systemd` but then cannot start `runit.service`.
   Ubuntu 24.04 failed earlier in convergence because `runit-systemd` had no install candidate.

README.md

@@ -18,78 +18,78 @@ This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of
 
 The following platforms are supported via test kitchen.
 
-- Ubuntu
-- Debian
-- RHEL
+* Ubuntu
+* Debian
+* RHEL
 
 It may work with or without modification on other platforms, particularly using the `source` install method.
 
 ## Chef
 
-- Chef 15.3+
+* Chef 15.3+
 
 ## Cookbooks
 
-- build-essential - for compiling the source.
-- ucspi-tcp - `tcpserver` is used by the axfr recipe.
-- runit - for setting up the services.
+* build-essential - for compiling the source.
+* ucspi-tcp - `tcpserver` is used by the axfr recipe.
+* runit - for setting up the services.
 
 ## Attributes
 
-- `node['djbdns']['tinydns_ipaddress']` - listen address for public facing tinydns server
-- `node['djbdns']['tinydns_internal_ipaddress']` - listen address for internal tinydns server
-- `node['djbdns']['public_dnscache_ipaddress']` - listen address for public DNS cache
-- `node['djbdns']['axfrdns_ipaddress']` - listen address for axfrdns
-- `node['djbdns']['public_dnscache_allowed_networks']` - subnets that are allowed to talk to the dnscache.
-- `node['djbdns']['tinydns_internal_resolved_domain']` - default domain this tinydns serves
-- `node['djbdns']['tinydns_internal_resolved_reverse_domains']` - default in-addr.arpa domains this tinydns serves
-- `node['djbdns']['axfrdns_dir']` - default location of the axfrdns service and configuration, default `/etc/djbdns/axfrdns`
-- `node['djbdns']['tinydns_dir']` - default location of the tinydns service and configuration, default `/etc/djbdns/tinydns`
-- `node['djbdns']['tinydns_internal_dir']` - default location of the tinydns internal service and configuration, default `/etc/djbdns/tinydns_internal`
-- `node['djbdns']['public_dnscache_dir']` - default location of the public dnscache service and configuration, default `/etc/djbdns/public-dnscache`
-- `node['djbdns']['bin_dir']` - default location where binaries will be stored.
-- `node['djbdns']['axfrdns_uid']` - default uid for the axfrdns user
-- `node['djbdns']['dnscache_uid']` - default uid for the dnscache user
-- `node['djbdns']['dnslog_uid']` - default uid for the dnslog user
-- `node['djbdns']['tinydns_uid']` - default uid for the tinydns user
-- `node['djbdns']['package_name']` - name of the djbdns package. this shouldn't be changed most of the time, but may be necessary to use the [Debian fork](http://en.wikipedia.org/wiki/Dbndns), `dbndns`.
-- `node['djbdns']['install_method']` - method used to install djbdns, can be `package`, or `source`.
+* `node['djbdns']['tinydns_ipaddress']` - listen address for public facing tinydns server
+* `node['djbdns']['tinydns_internal_ipaddress']` - listen address for internal tinydns server
+* `node['djbdns']['public_dnscache_ipaddress']` - listen address for public DNS cache
+* `node['djbdns']['axfrdns_ipaddress']` - listen address for axfrdns
+* `node['djbdns']['public_dnscache_allowed_networks']` - subnets that are allowed to talk to the dnscache.
+* `node['djbdns']['tinydns_internal_resolved_domain']` - default domain this tinydns serves
+* `node['djbdns']['tinydns_internal_resolved_reverse_domains']` - default in-addr.arpa domains this tinydns serves
+* `node['djbdns']['axfrdns_dir']` - default location of the axfrdns service and configuration, default `/etc/djbdns/axfrdns`
+* `node['djbdns']['tinydns_dir']` - default location of the tinydns service and configuration, default `/etc/djbdns/tinydns`
+* `node['djbdns']['tinydns_internal_dir']` - default location of the tinydns internal service and configuration, default `/etc/djbdns/tinydns_internal`
+* `node['djbdns']['public_dnscache_dir']` - default location of the public dnscache service and configuration, default `/etc/djbdns/public-dnscache`
+* `node['djbdns']['bin_dir']` - default location where binaries will be stored.
+* `node['djbdns']['axfrdns_uid']` - default uid for the axfrdns user
+* `node['djbdns']['dnscache_uid']` - default uid for the dnscache user
+* `node['djbdns']['dnslog_uid']` - default uid for the dnslog user
+* `node['djbdns']['tinydns_uid']` - default uid for the tinydns user
+* `node['djbdns']['package_name']` - name of the djbdns package. this shouldn't be changed most of the time, but may be necessary to use the [Debian fork](http://en.wikipedia.org/wiki/Dbndns), `dbndns`.
+* `node['djbdns']['install_method']` - method used to install djbdns, can be `package`, or `source`.
 
 ## Resources
 
 This cookbook is mid-migration from recipe/attribute-driven behavior toward higher-level resources. The current resource-first surface is:
 
-- `djbdns_install` - installs djbdns and bootstraps shared users/directories.
-- `djbdns_server` - configures the public tinydns service.
-- `djbdns_internal_server` - configures the internal tinydns service with explicit records or legacy data-bag/template inputs.
-- `djbdns_cache` - configures the public dnscache service.
-- `djbdns_axfr` - configures the axfrdns service that fronts an existing public tinydns directory.
-- `djbdns_rr` - appends tinydns records inside an existing tinydns root.
+* `djbdns_install` - installs djbdns and bootstraps shared users/directories.
+* `djbdns_server` - configures the public tinydns service.
+* `djbdns_internal_server` - configures the internal tinydns service with explicit records or legacy data-bag/template inputs.
+* `djbdns_cache` - configures the public dnscache service.
+* `djbdns_axfr` - configures the axfrdns service that fronts an existing public tinydns directory.
+* `djbdns_rr` - appends tinydns records inside an existing tinydns root.
 
 The legacy recipes `default`, `server`, `cache`, `internal_server`, and `axfr` are now compatibility wrappers around those resources.
 
 ### Resource Model Roadmap
 
-- `djbdns_install`: shared install/bootstrap layer
-- `djbdns_server`: public tinydns service
-- `djbdns_internal_server`: internal tinydns service with explicit data-bag/template inputs
-- `djbdns_cache`: public dnscache service
-- `djbdns_axfr`: axfr service bound to an existing public tinydns instance
+* `djbdns_install`: shared install/bootstrap layer
+* `djbdns_server`: public tinydns service
+* `djbdns_internal_server`: internal tinydns service with explicit data-bag/template inputs
+* `djbdns_cache`: public dnscache service
+* `djbdns_axfr`: axfr service bound to an existing public tinydns instance
 
 ## djbdns_rr
 
 Adds a resource record for the specified FQDN.
 
 ### Actions
 
-- `:add`: Creates a new entry in the tinydns data file with the `add-X` scripts in the tinydns root directory.
+* `:add`: Creates a new entry in the tinydns data file with the `add-X` scripts in the tinydns root directory.
 
 ### Attribute Parameters
 
-- `fqdn`: name attribute. specifies the fully qualified domain name of the record.
-- `ip`: ip address for the record.
-- `type`: specifies the type of entry. valid types are: alias, alias6, childns, host, host6, mx, and ns. default is `host`.
-- `cwd`: current working directory where the add scripts and data files must be located. default is the node attribute `djbdns[:tinydns_internal_dir]`, usually `/etc/djbdns/tinydns-internal`.
+* `fqdn`: name attribute. specifies the fully qualified domain name of the record.
+* `ip`: ip address for the record.
+* `type`: specifies the type of entry. valid types are: alias, alias6, childns, host, host6, mx, and ns. default is `host`.
+* `cwd`: current working directory where the add scripts and data files must be located. default is the node attribute `djbdns[:tinydns_internal_dir]`, usually `/etc/djbdns/tinydns-internal`.
 
 ### Example
 
@@ -112,14 +112,14 @@ Compatibility wrapper for `djbdns_install`.
 
 The default recipe attempts to install djbdns on as many platforms as possible. It tries to determine the platform's installation method:
 
-- Debian will install from packages
-- All other distributions will install from source.
+* Debian will install from packages
+* All other distributions will install from source.
 
 Service specific users will be created as system users:
 
-- dnscache
-- dnslog
-- tinydns
+* dnscache
+* dnslog
+* tinydns
 
 ## axfr