nickanderson

bundle agent php
{
	vars:
		"version" string => ifelse( "debian.!ubuntu", "8.0",
                                          "ubuntu", "8.2",
                                          "centos", "8.3",
                                          "freebsd", "82",
                                           " ¯\_(ツ)_/¯" );

nickanderson

variablesmatching_as_data() is useful for centralizing information from disparate sources. For example, deriving a list of package names by extracting the values from variables that match a specific name.

 bundle agent package_names_from_variablesmatching_as_data
 # @brief Example illustrating deriving a list of package names from variables named with a specific naming convention
{
  vars:
      "packages_baseline" slist => { "bash-completion", "emacs" };
      "packages_os" slist => { "httpd" };

nickanderson

@nickanderson The title piqued my interest so I had a read. Bearing in mind that I don't use cfengine,
so it's likely my fault for not understanding, but I would have liked to see how you do different
things _as_a_result_ of the different repaired vs kept vs reached scenarios.

Is it possible to do that? Say create a new file with contents that vary based on which of those
scenarios occured?

Thanks!

nickanderson

bundle agent __main__
{

    vars:
    "repo_data" data => '{"one": { "value": "something" }, "two": { "run_class": "linux" } }';
    "repo_names" slist => getindices(repo_data);
    reports:
          "$(this.bundle): yes or/not $(repo_names)"
              if => or(

nickanderson

bundle agent __main__
{
  vars:
    # one option for each of 28 days in a month.
    "options" slist => { expandrange( "selected_option_[1-28]", 1 ) };

  classes:
    "selected_option" select_class => { @(options) };

nickanderson

I have a long history of using org-mode, but I don’t have a consistent history of tracking it under version control. I have at times and then stopped, I don’t push my git repository anywhere, it does get backed up periodically. Some of my org-mode files get copied around to multiple devices (typically bi-directional sync, but you can get creative with send only and exclusions etc ..). Anyway, I have a few different git repositories that contain org-mode files and I wanted to visualize activity over time. Gource produces a nifty visualization, and you can even interact with it, zooming in, panning around while being able to see user, directory, and file names.

I use this city script to generate videos like https://www.youtube.com/watch?v=b7y0y6sWb2I

#!/bin/bash
set -e
set -u
set -x

nickanderson

Example illustrating use of regex_replace() to remove quiet from GRUB_CMDLINE_LINUX_DEFAULT

Use regex_replace() to remove quiet from GRUB_CMDLINE_LINUX_DEFAULT.

bundle agent __main__
{
    methods:
     "init";
     "test";

nickanderson

How to add custom policy to grant clients access to a custom directory and integrate via cfbs

To grant clients access to a new path via cf-serverd you need an access type promise.

We can create my-custom-access.cf with a server bundle and an access type promise:

bundle server my_custom_access
{

nickanderson

Example converting a traditionally managed 3.18.3 policy set to cfbs

Initalizing a traditionally managed policy set

First, we need to initialize a traditional policy set. Let’s start with masterfiles from the 3.18.3 release. This way we can go through the process of migrating to the same version with cfbs. We need to download it and unpack it into the root of our repository.

nickanderson

Here is an example of my daily capture templates. My work log (wll) is my most often used capture template. I have many other capture templates for things that recurr on a regular basis, like Meetings. The capture template for a specific meeting includes links to the common attendees individual note pages. These links surface that meeting if I visit an individuals note and run org-roam-buffer.

(setq org-roam-dailies-capture-templates
      `(

        ("w" "work")
        ("wl" "Log")
        ("wll" "Log" entry
         "* %?\n:properties:\n:prior_context: %a\n:end:\n"