The current design of simp_bolt confuses a user's default bolt.yaml with the bolt.yaml for a project directory, and can only configure a node for single user and purpose.
The controller node:
manages a local user home directory files .puppetlabs/bolt.yaml with default bolt settings
This cannot be edited by the user
It will be ignored when be ignored when using any project with its own bolt.yaml or Boltdir (most of them).
A local hiera.yaml and data under .puppetlabs
This is useless
The puppet code is broken into classes, which should be defined types wrapped by Puppet classes that can configure multiple nodesets of bolt administration that might include the same node as a target/controller.
Update: noted that bolt now has cascading config file that includes system and user settings:
(U) Details: https://github.com/puppetlabs/bolt/pull/1557
This affects the assumption of this issue, and probably the future architecture of the simp_bolt module.
Module manages a node as a Bolt 2.x controller:
ensure the puppet-bolt package
manage (at least one) system-wide bolt.yaml and inventory.yaml
system-wide inventory.yaml isn't a thing, but we can make it so by specifying the path in the system-wide bolt.yaml
as templates OR direct content
direct content provided as a `Hash`, so both methods can use the same template in the end
possibly manage additional inventory and bolt files
System-wide bolt.yaml paths:
Note to self: an example SIMP-related inventory.yaml: