From e2b879caff26e6dcb81412640f40767863831f66 Mon Sep 17 00:00:00 2001
From: alex <alex@pdp7.net>
Date: Wed, 1 Feb 2023 21:30:55 +0100
Subject: Document ugly things

---
 personal_infra/up.py | 31 +++++++++++++++++++++++++++++--
 1 file changed, 29 insertions(+), 2 deletions(-)

(limited to 'personal_infra/up.py')

diff --git a/personal_infra/up.py b/personal_infra/up.py
index 55d0f9bf..131fc9e6 100755
--- a/personal_infra/up.py
+++ b/personal_infra/up.py
@@ -8,17 +8,44 @@ import subprocess
 import textwrap
 import yaml
 
+
 """
+This script performs Puppet catalog compilation without a central server.
+
+It receives the following arguments:
+
+* directory: a working directory. The script expects to find some data, like
+  variables to use in the compilation process, facts, etc. The script also
+  generates intermediate files and output there.
+
+* modulepath: path to your modules directory
+* manifest: path to your site directory
+* host: the hosts to compile catalogs to
+
+The script expects the following content on the working directory:
+
 directory/
   global_vars/*.json: these JSON files will be available to all hosts
   host_vars/{host}/*.json: these JSON files will be available in each host
   facts/{host}.json: output from "facter -y" for each host
 
+And produces the following files:
+
 directory/
   output/
     {host}/
-      catalog.json
-      modules/
+      catalog.json: the compiled catalog for the host
+      modules: a copy of the module directory
+
+Just ship the {host} directory to each host and run:
+
+$ puppet apply --catalog .../catalog.json --modulepath=.../modules/
+
+Check the apply_catalog Ansible role for example usage.
+
+As we have the catalogs, we can manipulate them. See
+pseudo_resource_exporter.py for an example hack. We can simulate exported
+resources without PuppetDB.
 """
 
 
-- 
cgit v1.2.3