Updates to schema

src/docs.html

@@ -96,7 +96,7 @@
                   <li>Detect installed packages and services</li>
                   <li>Collect config that deviates from packaged defaults (where possible)</li>
                   <li>Grab relevant custom/unowned files in service dirs</li>
-                  <li>Capture non-system users & SSH public keys</li>
+                  <li>Capture non-system users & SSH public keys, .bashrc files etc</li>
                 </ul>
               </div>
             </div>
@@ -136,9 +136,10 @@
             <li>For each package, it tries to detect files in <code>/etc</code> that have been modified from the default that get shipped with the package.</li>
             <li>It detects running/enabled services and timers via systemd. For each of these, it looks for the unit files, any 'drop-in' files, environment variable files, etc, as well as what executable it executes, and tries to map those systemd services to the packages it's already learned about earlier (that way, those 'packages' or future Ansible roles, can also be associated with 'handlers' in Ansible, to handle restart of the services if/when the configs change)</li>
             <li>Aside from known packages already learned, it optimistically tries to capture extra system configuration in <code>/etc</code> that is common for config management. This is stuff like the apt or dnf configuration, crons, logrotate configs, networking settings, hosts files, etc.</li>
+	    <li>For applications that commonly make use of symlinks (think Apache2 or Nginx's <code>sites-enabled</code> or <code>mods-enabled</code>, it notes what symlinks exist so that it can capture those in Ansible</li>
             <li>It also looks for other snowflake stuff in <code>/etc</code> not associated with packages/services or other typical system config, and will put these into an <code>etc_custom</code> role.</li>
             <li>Likewise, it looks in <code>/usr/local</code> for stuff, on the assumption that this is an area that custom apps/configs might've been placed in. These go into a <code>usr_local_custom</code> role.</li>
-            <li>It captures non-system user accounts, their group memberships and their <code>.ssh/authorized_keys</code></li>
+	    <li>It captures non-system user accounts, their group memberships and files such as their <code>.ssh/authorized_keys</code>, and <code>.bashrc</code>, <code>.profile</code>, <code>.bash_aliases</code>, <code>.bash_logout</code> if these files differ from the <code>skel</code> defaults</li>
             <li>It takes into account anything the user set with <code>--exclude-path</code> or <code>--include-path</code>. For anything extra that is included, it will put these into an '<code>extra_paths</code>' role. The location could be anywhere e.g something in <code>/opt</code>, <code>/srv</code>, whatever you want.</li>
             <li>It writes the state.json and captures the artifacts.</li>
           </ul>
@@ -146,7 +147,7 @@
           <p class="text-secondary">Other things to be aware of:</p>
           <ul class="mb-0 small">
             <li>You can use multiple invocations of <code>--exclude-path</code> to skip the bits you don't want. You also can always comment out from the playbook.yml or delete certain roles it generates once you've run the <code>enroll manifest</code>.</li>
-            <li>In terms of safety measures: it doesn't traverse symlinks, and it has an 'IgnorePolicy' that makes it ignore most binary files (except GPG binary keys used with apt) - though if you specify certain paths with <code>--include-path</code> and use <code>--dangerous</code>, it will skip some policy statements such as what types of content to ignore.</li>
+            <li>In terms of safety measures: it doesn't traverse into symlinks, and it has an 'IgnorePolicy' that makes it ignore most binary files (except GPG binary keys used with apt) - though if you specify certain paths with <code>--include-path</code> and use <code>--dangerous</code>, it will skip some policy statements such as what types of content to ignore.</li>
             <li>It will skip files that are too large, and it also currently has a hardcoded cap of the number of files that it will harvest (4000 for <code>/etc</code>, <code>/usr/local/etc</code> and <code>/usr/local/bin</code>, and 500 files per 'role'), to avoid unintentional 'runaway' situations.</li>
 	    <li>If you are using the 'remote' mode to harvest, and your remote user requires a password for sudo, you can pass in <code>--ask-become-pass</code> (or <code>-K</code>) and it will prompt for the password. If you forget, and remote requires password for sudo, it'll still fall back to prompting for a password, but will be a bit slower to do so.</li>
           </ul>

src/schema/state.schema.json

@@ -60,10 +60,12 @@
           "enum": [
             "user_excluded",
             "unreadable",
+	    "backup_file",
             "log_file",
             "denied_path",
             "too_large",
             "not_regular_file",
+            "not_symlink",
             "binary_like",
             "sensitive_content"
           ],
@@ -212,6 +214,10 @@
             "systemd_dropin",
             "systemd_envfile",
             "user_include",
+            "user_profile",
+            "user_shell_aliases",
+            "user_shell_logout",
+            "user_shell_rc",
             "usr_local_bin_script",
             "usr_local_etc_custom",
             "yum_conf",
@@ -236,6 +242,32 @@
       ],
       "type": "object"
     },
+    "ManagedLink": {
+      "additionalProperties": false,
+      "type": "object",
+      "properties": {
+        "path": {
+          "type": "string",
+          "minLength": 1,
+          "pattern": "^/.*"
+        },
+        "target": {
+          "type": "string",
+          "minLength": 1
+        },
+        "reason": {
+          "type": "string",
+          "enum": [
+            "enabled_symlink"
+          ]
+        }
+      },
+      "required": [
+        "path",
+        "target",
+        "reason"
+      ]
+    },
     "ObservedVia": {
       "oneOf": [
         {
@@ -371,6 +403,12 @@
           },
           "type": "array"
         },
+        "managed_links": {
+          "items": {
+            "$ref": "#/$defs/ManagedLink"
+          },
+          "type": "array"
+        },
         "notes": {
           "items": {
             "type": "string"