.

git-vendor-name: mo
git-vendor-dir: vendor/git.knownelement.com/ExternalVendorCode/mo
git-vendor-repository: https://git.knownelement.com/ExternalVendorCode/mo.git
git-vendor-ref: master

.gitignore

@@ -1,8 +1,2 @@
-build-output/client-submission/*.md
-build-output/client-submission/*.pdf
-build-output/client-submission/*.doc
-build-output/job-board/*.md
-build-output/job-board/*.pdf
-build-output/job-board/*.doc
-build-temp/*.yml
-build-temp/*.md
+build-output/*
+build-temp/*

README.md

@@ -1,3 +1,53 @@
 # MarkdownResume-Pipeline
 
-A set of scripts and template files for managing a markdown/json resume. 
+- [MarkdownResume-Pipeline](#markdownresume-pipeline)
+  - [Introduction](#introduction)
+  - [Directory Overview](#directory-overview)
+  - [Build pipeline](#build-pipeline)
+    - [Outputs](#outputs)
+  - [Production Use](#production-use)
+
+## Introduction
+
+Resume formatting/publication/management is difficult, tedious, annoying etc. The @ReachableCEO has hacked the process and made it easy! This repository is the core build scripts, templates etc used for resume management. It's meant as one half of a complete solution.
+
+Please see [MarkdownResum-Pipeline-ClientExample repository](https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline-ClientExample) for the other half. You would clone that repository and follow the instructions. That repository has this repository vendored into it.
+
+## Directory Overview
+
+- build: build script and associated support files.
+- build-output: markdown file for pandoc gets placed here. If you want to make formatting changes before conversion to PDF/Word, you can do so.
+- build-temp: working directory for the build process. In case you need to debug an intermediate step.
+- Templates
+  - CandidateInfoSheet: contains the markdown/yaml template files for a candidate information sheet. This allows you to produce a standardized reply to recruiters to eliminate an average of 6 emails/phone calls per inbound lead. It has a rate sheet and all the standard "matrix" tables they need to fill out for submission to an end client (or, in reality, to the US based recruiting team who interfaces with the client).
+  - ContactInfo: contact info (one version for the recruiter facing resume, one version for client facing).
+  - JobHistoryDetails: details for each position listed in WorkHistory/WorkHistory.csv.
+  - SkillsAndProjects: This contains what the name says. Holds a skills.csv file that gets turned into a skills table and a projects file that gets placed at beginning of resume as a career highlights section.
+  - WorkHistory: contains the WorkHistory.csv file used by the build script to generate Employment History section.
+
+## Build pipeline
+
+In the build directory:
+
+- build-demo.sh - End to end self contained build example for testing the repository after changes to templates.
+- build-pipeline-server.sh - Used by client repository to builds three assets:
+  - PDF/Word for submitting to job portals
+  - PDF/Word for submitting to end clients (strips cover sheet/contact info)
+  - PDF of the candidate information sheet.
+- BuildTemplate-* : Templatized YAML metadata files that get rendered during the build process to be used by Pandoc.
+- resume-docx-reference.docx: Template "style" file for Word output.
+
+### Outputs
+
+- Word format output is a best effort . The style file was sourced from : <https://sdsawtelle.github.io/blog/output/simple-markdown-resume-with-pandoc-and-wkhtmltopdf.html> (vendored in vendor/git.knownelement.com/ExternalVendorCode/markdown-resume just in case)
+- PDF output considered production. Please see: <https://github.com/Wandmalfarbe/pandoc-latex-template> (vendored in vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template ) and <https://github.com/ReachableCEO/rcdoc-pipeline> if you want to re-create/modify the build pipeline for your own markdown project.
+
+## Production Use
+
+This system is in production use by the @ReachableCEO:
+
+- [MarkdownResume-ClientExample-ReachableCEO](https://git.knownelement.com/reachableceo/MarkdownResume-ReachableCEO)
+- [ReachableCEO Career Site](https://resume.reachableceo.com)
+- uploaded to all major job portals
+
+This was a labor of love by the @ReachableCEO in the hopes others can massively optimize the job hunt process.

Templates/CandidateInfoSheet/CandidateInfoSheet.md

@@ -1,110 +0,0 @@
-# Charles N Wyble
-
-## Introduction
-
-Hello,
-
-I apologize for the form letter response.
-
-I receive a high volume of recruiter emails every day and I've found this letter to be the most efficient way to
-handle the high volume of emails and reduce back and forth emails/texts/calls.
-
-If you have any questions/comments/concerns not covered by this document, please let me know via e-mail and I'm happy to address them!
-
-If you ask me something answered in this document, I will not respond and will not move forward with the opportunity, so please read it in detail!
-
-## Re: share my ID over email
-
-I WILL NOT share my (full or redacted) photo ID over email or any other electronic written  
-communication. If that is "required" then I have no interest in moving forward with this opportunity.
-
-I am happy to get on a teams/zoom/google meet etc call and show my ID.
-
-## Re: professional references
-
-I am happy to provide professional references once an interview with the end client/customer/hiring manager/team has been scheduled. I will NOT provide references up front. If that is "required" then I have no interest in moving forward with this opportunity.
-
-## Re: relocation
-
-if the role is not based in **Austin TX** or **Raleigh NC** I will need to re-locate
-
-| Question                                  | Answer |
-|-------------------------------------------|--------|
-| Am I open to relocation?                  | Yes    |
-| Am I willing to re-locate at own expense? | No     |
-| Am I open to up to 100% travel            | Yes    |
-
-Please be aware that:
-
-- I will **only re-locate at the employer expense**.
-- I will need **two weeks of time** to re-locate.
-- The net amount of the re-location benefit **MUST be at least $5,000 USD** to fully compensate me for the time/effort to re-locate.
-- The full re-location benefit **must be provided prior to the confirmed start date**.
-- I **will NOT** accept a reimbursement based re-location package.
-- I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
-
-\pagebreak
-
-## Rate Schedule (compensation expectations)
-
-For **fully remote** roles only:
-
-I am open to (at the absolute minimum): **\$50.00 per hour(w2)/\$75.00 per hour (1099/corp to corp)/ $100,000.00 annually (w2)**. 
-
-I have a strong preference for roles that are : **\$65.00 per hour(w2)/\$85.00 per hour (1099/corp to corp)/ $130,000.00 annually (w2)**.
-
-For **on-site roles**:
-
-I am open to (at the absolute minimum): **\$75.00 per hour(w2)/\$95.00 per hour (1099/corp to corp)/ $150,000.00 annually (w2)**.
-
-In regards to compensation structure, I am open to:
-
-- w2
-- corp to corp (I have my own LLC)
-- 1099  
-
-If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
-
-If it's a different rate with/without benefits, send both.
-
-If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
-
-\pagebreak
-
-## Details needed for submission
-
-### My resume
-
-[Download Charles resume(pdf)](https://resume.reachableceo.com/job-board/CharlesNWyble-Resume.pdf)
-
-I am happy to discuss and make edits to the resume content specific to the opportunity if you feel
-they are needed.
-
-### Candidate details  
-
-Here are my complete candidate details for submission to the role.
-
-| Question                              | Answer                                                                   |
-|---------------------------------------|--------------------------------------------------------------------------|
-| Full name                             | Charles Wyble                                                            |
-| E-mail address                        | <reachableceo@reachableceo.com>                                          |
-| Phone number                          | 818-280-7059                                                             |
-| Preferred form of contact             | E-mail will get the fastest response                                     |
-| Work authorization                    | US Citizen                                                               |
-| Are you employed presently?           | No                                                                       |
-| Current location                      | Austin, Texas                                                            |
-| Current timezone                      | CST                                                                      |
-| Timezones I can work in               | PST/CST/EST                                                              |
-| Availability to interview             | Immediate                                                                |
-| Availability to start                 | Immediate for remote/local, two weeks for relocation                     |
-| Open to in-office/hybrid/remote       | Yes                                                                      |
-| Any trips planned in next six months? | No                                                                       |
-| Highest Education                     | High School (no college/university)                                      |
-| Graduated Year                        | 2002                                                                     |
-| Name of school                        | Osborne Christian School                                                 |
-| Location of school                    | Los Angeles CA                                                           |
-| Linkedin Profile                      | [Linkedin Profile](https://www.linkedin.com/in/charles-wyble-412007337/) |
-| Github Profile                        | [Github Profile](https://www.github.com/ReachableCEO/)                   |
-| Last project                          | Contract, ended October 2024                                             |
-| DOB                                   | 09/14                                                                    |
-| Total IT/career experience            | 22 years                                                                 |

Templates/CandidateInfoSheet/CandidateInfoSheet.yml

@@ -1,14 +0,0 @@
-title: "Charles N Wyble Candidate Details"
-titlepage: true
-titlepage-logo: "D:/tsys/@ReachableCEO/ReachableCEO.png"
-toc: true
-toc-own-page: true
-date: \today
-header-left: "\\hspace{1cm}"
-header-center: "\\leftmark"
-header-right: "Page \\thepage"
-footer-left: "Charles N Wyble"
-footer-center: "Tenacity. Velocity. Focus."
-footer-right: "[Source code for this file](https://github.com/ReachableCEO/ReachableCEOResume/blob/main/ancillary-support-files/CharlesNWybleCandidateInfo.md)"
-urlcolor: blue
-page-background: "D:/tsys/@ReachableCEO/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background1.pdf"

Templates/ContactInfo/ContactInfo-ClientSubmit.md

@@ -1,4 +0,0 @@
-{{CandidateName}}
-=====
-
-{{CandidateOneLinerSummary}}

Templates/ContactInfo/ContactInfo-JobBoard.md

@@ -1,6 +0,0 @@
-{{CandidateName}}
-=====
-
-{{CandidateOneLinerSummary}}
-
-[ [Github Profile]({{CandidateGithub}}) ] .  [ [Linkedin Profile]({{CandidateLinkedin}}) ] . [ {{CandidateEmail}} ] . [ {{CandidatePhone}} ] . [ {{CandidateLocation}} ]

Templates/JobHistoryDetails/job1.md

@@ -1,3 +0,0 @@
-- Stuff
-- Things
-- Amazing project!

Templates/JobHistoryDetails/job2.md

@@ -1,3 +0,0 @@
-- Stuff
-- Things
-- Amazing project!

Templates/SkillsAndProjects/Projects.md

@@ -1,2 +0,0 @@
-- Cool project 1.
-- cool project 2.

Templates/SkillsAndProjects/Skills.csv

@@ -1,2 +0,0 @@
-skill1|1 years|skill,1,details,and,stuff
-skill2|2 years|skill2,2,details,and,stuff,and,things

Templates/WorkHistory/WorkHistory.csv

@@ -1,2 +0,0 @@
-job1,Title of job 1,January 1 1970 - January 6 1980
-job2,Title of Job 2,January 1 1970 - January 6 1980

build-output/client-submission/ignore-this-dir

@@ -1 +0,0 @@
-This directory is used by the build process. Ignore it.

build-output/ignore-this-dir

@@ -1 +0,0 @@
-Working directory for the pipeline. Don't use.

build-output/job-board/ignore-this-dir

@@ -1 +0,0 @@
-This directory is used by the build process. Ignore it.

build-temp/ignore-this-dir

@@ -1 +0,0 @@
-Working directory for the pipeline. Don't use.

build/BuildTemplate-ClientSubmission.yml

@@ -1,7 +0,0 @@
-title: "{{CandidateName}} Resume"
-header-left: "\\hspace{1cm}"
-header-center: "\\leftmark"
-header-right: "Page \\thepage"
-footer-left: "{{CandidateName}}"
-urlcolor: {{URLCOLOR}}
-page-background: "{{PAGEBACKGROUND}}"

build/BuildTemplate-JobBoard.yml

@@ -1,12 +0,0 @@
-title: "{{CandidateName}} Resume"
-titlepage: true
-titlepage-logo: "{{CandidateLogo}}"
-date: \today
-header-left: "\\hspace{1cm}"
-header-center: "\\leftmark"
-header-right: "Page \\thepage"
-footer-left: "{{CandidateName}}"
-footer-center: "{{CandidateTagline}}"
-footer-right: "[Source code for this resume]({{ResumeSourceCode}})"
-urlcolor: {{URLCOLOR}}
-page-background: "{{PAGEBACKGROUND}}"

build/build-pipeline-server-json.sh

@@ -0,0 +1,339 @@
+#!/bin/bash
+
+#####################################################################################################
+#JSON Resume
+#####################################################################################################
+
+####################################################
+####################################################
+####################################################
+#DO NOT CHANGE ANYTHING BELOW THIS LINE
+####################################################
+####################################################
+####################################################
+
+add_open_section() 
+
+{
+
+echo "{" > $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_meta_section()
+
+{
+
+cat << META >> $BUILD_OUTPUT_DIR/resume.json
+  "meta": {
+    "theme": "$JSONRESUME_THEME"
+  },
+META
+
+}
+
+
+
+add_basics_section() 
+
+{
+
+cat << BASICS >> $BUILD_OUTPUT_DIR/resume.json
+
+  "basics": {
+    "name": "$CandidateName",
+    "phone": "$CandidatePhone",
+    "label": "$CandidateRole",
+    "image": "$CandidateAvatar",
+    "summary": "$CandidateOneLineSummary",
+    "website": "$CandidateWebsite",
+    "url": "https://lordajax.com",
+    "email": "$CandidateEmail",
+    "location": {
+      "city": "$CandidateLocation",
+      "countryCode": "$CandidateCountry"
+    },
+  },
+BASICS
+
+}
+
+
+# Bash Function to Append JSON
+add_profiles_section () 
+
+{
+
+  echo '{"profiles": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r username url network; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "username": "$username",
+      "url": "$url",
+      "network": "$network"
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/profiles.csv
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_certificates_section() 
+
+{
+
+  echo '{"certificates": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r name date issuer url; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "name": "$name",
+      "date": "$date",
+      "issuer": "$issuer",
+      "url": "$url"
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/certificates.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_education_section() 
+
+{
+
+  echo '{"education": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r institution url area studyType startDate endDate score courses; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "institution": "$institution",
+      "url": "$url",
+      "area": "$area",
+      "studyType": "$studyType",
+      "startDate": "$startDate",
+      "endDate": "$endDate",
+      "score": "$score",
+      "courses": [$(echo "$courses" | sed 's/;/","/g' | sed 's/^/"/;s/$/"/')]
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/education.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_references_section() 
+
+{
+
+  echo '{"references": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r reference name; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "reference": "$reference",
+      "name": "$name"
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/references.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_skills_section() 
+
+{
+
+  echo '{"skills": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r name level keywords; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "name": "$name",
+      "level": "$level",
+      "keywords": [$(echo "$keywords" | sed 's/;/","/g' | sed 's/^/"/;s/$/"/')]
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/skills.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_awards_section() 
+
+{
+
+  echo '{"awards": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r title awarder date summary; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "title": "$title",
+      "awarder": "$awarder",
+      "date": "$date",
+      "summary": "$summary"
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/awards.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_publications_section() 
+
+{
+
+  echo '{"publications": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r name publisher releaseDate url summary; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "name": "$name",
+      "publisher": "$publisher",
+      "releaseDate": "$releaseDate",
+      "url": "$url",
+      "summary": "$summary"
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/publications.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_volunteer_section() 
+
+{
+
+  echo '{"volunteer": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r organization position url startDate summary highlights; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "organization": "$organization",
+      "position": "$position",
+      "url": "$url",
+      "startDate": "$startDate",
+      "summary": "$summary",
+      "highlights": [$(echo "$highlights" | sed 's/;/","/g' | sed 's/^/"/;s/$/"/')]
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/volunteer.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_work_section() 
+
+{
+
+  echo '{"work": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r name position location website startDate endDate summary highlights; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "name": "$name",
+      "position": "$position",
+      "location": "$location",
+      "website": "$website",
+      "startDate": "$startDate",
+      "endDate": "$endDate",
+      "summary": "$summary",
+      "highlights": [$(echo "$highlights" | sed 's/;/","/g' | sed 's/^/"/;s/$/"/')]
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/work.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+
+add_languages_section() 
+
+{
+
+  echo '{"languages": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r language fluency; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "language": "$language",
+      "fluency": "$fluency"
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/languages.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_interests_section() 
+
+{
+
+  echo '{"interests": [' >> $BUILD_OUTPUT_DIR/resume.json
+  while IFS=, read -r name keywords; do
+    cat <<EOF >> $BUILD_OUTPUT_DIR/resume.json
+    {
+      "name": "$name",
+      "keywords": [$(echo "$keywords" | sed 's/;/","/g' | sed 's/^/"/;s/$/"/')]
+    },
+EOF
+  done < $JSON_TEMPLATE_DIRECTORY/interests.csv
+
+  # Remove trailing comma and close JSON array
+  sed -i '$ s/},/}/' $BUILD_OUTPUT_DIR/resume.json
+  echo ']}' >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+add_close_section() 
+
+{
+
+echo "}" >> $BUILD_OUTPUT_DIR/resume.json
+
+}
+
+main()
+
+{
+
+  add_open_section
+  add_meta_section 
+  add_basics_section 
+  add_profiles_section 
+  add_work_section 
+  add_volunteer_section 
+  add_education_section 
+  add_awards_section 
+  add_certificates_section 
+  add_publications_section 
+  add_skills_section 
+  add_languages_section 
+  add_interests_section 
+  add_references_section 
+  add_close_section
+
+}
+
+
+main

build/build-pipeline-server-markdown.sh

@@ -0,0 +1,164 @@
+#!/usr/bin/env bash
+
+set -euo pipefail
+
+#####################################################################################################
+#Markdown to PDF/MSWord Resumek and candidate info sheet
+#####################################################################################################
+
+#############################################
+# Create the candidate information PDF
+#############################################
+
+# Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
+
+$MO_PATH $YamlInputTemplateFileJobBoard > $BUILDYAML_JOBBOARD
+$MO_PATH $YamlInputTemplateFileClientSubmission > $BUILDYAML_CLIENTSUBMISSION
+$MO_PATH $YamlInputTemplateFileClientSubmission > $BUILDYAML_CANDIDATEINFOSHEET
+
+echo "Creating candidate info sheet..."
+
+$MO_PATH $PipelineClientWorkingDir/Templates/MarkdownResume/CandidateInfoSheet/CandidateInfoSheet.md > "$CandidateInfoSheetMarkdownOutputFile"
+
+pandoc \
+"$CandidateInfoSheetMarkdownOutputFile" \
+--template $PANDOC_TEMPLATE \
+--metadata-file="$BUILDYAML_CANDIDATEINFOSHEET" \
+--from markdown \
+--to=pdf \
+--output $CandidateInfoSheetPDFOutputFile
+
+
+
+echo "Combining markdown files into single input file for pandoc..."
+
+# Create contact info md file
+$MO_PATH "$PipelineClientWorkingDir/Templates/MarkdownResume/ContactInfo/ContactInfo-JobBoard.md" > "$BUILD_TEMP_DIR/ContactInfo-JobBoard.md"
+$MO_PATH "$PipelineClientWorkingDir/Templates/MarkdownResume/ContactInfo/ContactInfo-ClientSubmit.md" > "$BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md"
+
+#Pull in contact info
+cat "$BUILD_TEMP_DIR/ContactInfo-JobBoard.md" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+cat "$BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+echo "## Career Highlights" >> "$JobBoardMarkdownOutputFile"
+echo "## Career Highlights" >> "$ClientSubmissionMarkdownOutputFile"
+
+cat "$PipelineClientWorkingDir/Templates/MarkdownResume/SkillsAndProjects/Projects.md" >> "$JobBoardMarkdownOutputFile"
+echo "\pagebreak" >> "$JobBoardMarkdownOutputFile"
+
+cat  "$PipelineClientWorkingDir/Templates/MarkdownResume/SkillsAndProjects/Projects.md" >> "$ClientSubmissionMarkdownOutputFile"
+echo "\pagebreak" >> "$ClientSubmissionMarkdownOutputFile"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "## Employment History" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+echo "## Employment History" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+#And here we do some magic...
+#Pull in :
+
+# employer
+# title
+# start/end dates of employment 
+# long form position summary data from each position
+
+IFS=$'\n\t'
+for position in \
+$(cat "$PipelineClientWorkingDir/Templates/MarkdownResume/WorkHistory/WorkHistory.csv"); do
+
+COMPANY="$(echo $position|awk -F ',' '{print $1}')"
+TITLE="$(echo $position|awk -F ',' '{print $2}')"
+DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+cat "$PipelineClientWorkingDir/Templates/MarkdownResume/JobHistoryDetails/$COMPANY.md" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+cat "$PipelineClientWorkingDir/Templates/MarkdownResume/JobHistoryDetails/$COMPANY.md" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+done
+
+#Pull in my skills and generate a beautiful table.
+
+echo "\pagebreak" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "## Skills" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo "\pagebreak" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+echo "## Skills" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+#Table heading
+echo "|Skill|Experience|Skill Details|" >> "$JobBoardMarkdownOutputFile"
+echo "|---|---|---|" >> "$JobBoardMarkdownOutputFile"
+
+echo "|Skill|Experience|Skill Details|" >> "$ClientSubmissionMarkdownOutputFile"
+echo "|---|---|---|" >> "$ClientSubmissionMarkdownOutputFile"
+
+#Table rows
+IFS=$'\n\t'
+for skill in \
+$(cat "$PipelineClientWorkingDir/Templates/MarkdownResume/SkillsAndProjects/Skills.csv"); do
+SKILL_NAME="$(echo $skill|awk -F '|' '{print $1}')"
+SKILL_YEARS="$(echo $skill|awk -F '|' '{print $2}')"
+SKILL_DETAIL="$(echo $skill|awk -F '|' '{print $3}')"
+echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> "$JobBoardMarkdownOutputFile"
+echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> "$ClientSubmissionMarkdownOutputFile"
+
+done
+unset IFS
+
+echo "Generating PDF output for job board version..."
+
+pandoc \
+"$JobBoardMarkdownOutputFile" \
+--template $PANDOC_TEMPLATE \
+--metadata-file="$BUILDYAML_JOBBOARD" \
+--from markdown \
+--to=pdf \
+--output "$JobBoardPDFOutputFile"
+
+echo "Generating PDF output for client submission version..."
+
+pandoc \
+"$ClientSubmissionMarkdownOutputFile" \
+--template "$PANDOC_TEMPLATE" \
+--metadata-file="$BUILDYAML_CLIENTSUBMISSION" \
+--from markdown \
+--to=pdf \
+--output "$ClientSubmissionPDFOutputFile"
+
+echo "Generating MSWord output for job board version..."
+
+pandoc \
+"$JobBoardMarkdownOutputFile" \
+--metadata-file="$BUILDYAML_JOBBOARD" \
+--from markdown \
+--to=docx \
+--reference-doc="$WordOutputReferenceDoc" \
+--output "$JobBoardMSWordOutputFile"
+
+echo "Generating MSWord output for client submission version..."
+
+pandoc \
+"$ClientSubmissionMarkdownOutputFile" \
+--metadata-file="$BUILDYAML_CLIENTSUBMISSION" \
+--from markdown \
+--to=docx \
+--reference-doc="$WordOutputReferenceDoc" \
+--output "$ClientSubmissionMSWordOutputFile"

build/build.sh

@@ -1,188 +0,0 @@
-#!/usr/bin/env bash
-
-export CandidateName="First Middle Last"
-export CandidatePhone="1 123 456 7890"
-export CandidateLocation="Place 1/Place 2"
-export CandidateEmail="candidate@domain.com"
-export CandidateOneLineSummary="Super awesome and stuff."
-export CandidateLinkedin="linkedin.com"
-export CandidateGithub="github.com"
-export CandidateLogo=""
-export CandidateTagline="Your.Tagline.Here."
-export ResumeSourceCode="https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline"
-export URLCOLOR="blue"
-export PAGEBACKGROUND="../vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background3.pdf"
-
-####################################################
-#DO NOT CHANGE ANYTHING BELOW THIS LINE
-####################################################
-
-# shellcheck disable=SC1091
-#source "$(dirname "${BASH_SOURCE[0]}")/bash3boilerplate.sh"
-
-############################################################
-# Setup globals
-############################################################
-
-readonly BUILD_OUTPUT_DIR="../build-output"
-readonly BUILD_TEMP_DIR="../build-temp"
-readonly BUILDYAML_JOBBOARD="$BUILD_TEMP_DIR/JobBoard.yml"
-readonly BUILDYAML_CLIENTSUBMISSION="$BUILD_TEMP_DIR/ClientSubmission.yml"
-
-echo "Cleaning up from previous runs..."
-
-JobBoardMarkdownOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.md"
-JobBoardPDFOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.pdf"
-JobBoardMSWordOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.doc"
-
-ClientSubmissionMarkdownOutputFile="$BUILD_OUTPUT_DIR/client-submission/Resume.md"
-ClientSubmissionPDFOutputFile="$BUILD_OUTPUT_DIR/client-submission//Resume.pdf"
-ClientSubmissionMSWordOutputFile="$BUILD_OUTPUT_DIR/client-submission/Resume.doc"
-
-rm $BUILDYAML_JOBBOARD
-rm $JobBoardMarkdownOutputFile
-rm $JobBoardPDFOutputFile
-rm $JobBoardMSWordOutputFile
-
-rm $BUILDYAML_CLIENTSUBMISSION
-rm $ClientSubmissionMarkdownOutputFile
-rm $ClientSubmissionPDFOutputFile
-rm $ClientSubmissionMSWordOutputFile
-
-# Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
-
-./mo ./BuildTemplate-JobBoard.yml > $BUILDYAML_JOBBOARD
-./mo ./BuildTemplate-ClientSubmission.yml > $BUILDYAML_CLIENTSUBMISSION
-
-echo "Combining markdown files into single input file for pandoc..."
-
-# Create contact info md file
-./mo ../Templates/ContactInfo/ContactInfo-JobBoard.md > $BUILD_TEMP_DIR/ContactInfo-JobBoard.md
-./mo ../Templates/ContactInfo/ContactInfo-ClientSubmit.md > $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md
-
-#Pull in contact info
-cat $BUILD_TEMP_DIR/ContactInfo-JobBoard.md >> $JobBoardMarkdownOutputFile
-echo " " >> $JobBoardMarkdownOutputFile
-
-cat $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md >> $ClientSubmissionMarkdownOutputFile
-echo " " >> $ClientSubmissionMarkdownOutputFile
-
-echo "## Career Highlights" >> $JobBoardMarkdownOutputFile
-echo "## Career Highlights" >> $ClientSubmissionMarkdownOutputFile
-
-cat ../Templates/SkillsAndProjects/Projects.md >> $JobBoardMarkdownOutputFile
-echo "\pagebreak" >> $JobBoardMarkdownOutputFile
-
-cat ../Templates/SkillsAndProjects/Projects.md >> $ClientSubmissionMarkdownOutputFile
-echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
-
-echo " " >> $JobBoardMarkdownOutputFile
-echo "## Employment History" >> $JobBoardMarkdownOutputFile
-echo " " >> $JobBoardMarkdownOutputFile
-
-echo " " >> $ClientSubmissionMarkdownOutputFile
-echo "## Employment History" >> $ClientSubmissionMarkdownOutputFile
-echo " " >> $ClientSubmissionMarkdownOutputFile
-
-#And here we do some magic...
-#Pull in :
-
-# employer
-# title
-# start/end dates of employment 
-# long form position summary data from each position
-
-IFS=$'\n\t'
-for position in \
-$(cat ../Templates/WorkHistory/WorkHistory.csv); do
-
-COMPANY="$(echo $position|awk -F ',' '{print $1}')"
-TITLE="$(echo $position|awk -F ',' '{print $2}')"
-DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')"
-
-echo " " >> "$JobBoardMarkdownOutputFile"
-echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $JobBoardMarkdownOutputFile
-echo " " >> "$JobBoardMarkdownOutputFile"
-
-echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $ClientSubmissionMarkdownOutputFile
-echo " " >> "$ClientSubmissionMarkdownOutputFile"
-
-echo " " >> "$JobBoardMarkdownOutputFile"
-cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$JobBoardMarkdownOutputFile"
-echo " " >> "$JobBoardMarkdownOutputFile"
-
-cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$ClientSubmissionMarkdownOutputFile"
-echo " " >> "$ClientSubmissionMarkdownOutputFile"
-done
-
-#Pull in my skills and generate a beautiful table.
-
-echo "\pagebreak" >> $JobBoardMarkdownOutputFile
-echo " " >> "$JobBoardMarkdownOutputFile"
-echo "## Skills" >> "$JobBoardMarkdownOutputFile"
-echo " " >> "$JobBoardMarkdownOutputFile"
-
-echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
-echo " " >> "$ClientSubmissionMarkdownOutputFile"
-echo "## Skills" >> "$ClientSubmissionMarkdownOutputFile"
-echo " " >> "$ClientSubmissionMarkdownOutputFile"
-
-#Table heading
-echo "|Skill|Experience|Skill Details|" >> $JobBoardMarkdownOutputFile
-echo "|---|---|---|" >> $JobBoardMarkdownOutputFile
-
-echo "|Skill|Experience|Skill Details|" >> $ClientSubmissionMarkdownOutputFile
-echo "|---|---|---|" >> $ClientSubmissionMarkdownOutputFile
-
-#Table rows
-IFS=$'\n\t'
-for skill in \
-$(cat ../Templates/SkillsAndProjects/Skills.csv); do
-SKILL_NAME="$(echo $skill|awk -F '|' '{print $1}')"
-SKILL_YEARS="$(echo $skill|awk -F '|' '{print $2}')"
-SKILL_DETAIL="$(echo $skill|awk -F '|' '{print $3}')"
-echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $JobBoardMarkdownOutputFile
-echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $ClientSubmissionMarkdownOutputFile
-
-done
-unset IFS
-
-echo "Generating PDF output for job board version..."
-
-pandoc \
-"$JobBoardMarkdownOutputFile" \
---template eisvogel \
---metadata-file="../build-temp/JobBoard.yml" \
---from markdown \
---to=pdf \
---output $JobBoardPDFOutputFile
-
-echo "Generating MSWord output for job board version..."
-
-pandoc \
-"$JobBoardMarkdownOutputFile" \
---metadata-file="../build-temp/JobBoard.yml" \
---from markdown \
---to=docx \
---reference-doc=resume-docx-reference.docx \
---output $JobBoardMSWordOutputFile
-
-echo "Generating PDF output for client submission version..."
-
-pandoc \
-"$ClientSubmissionMarkdownOutputFile" \
---template eisvogel \
---metadata-file="../build-temp/ClientSubmission.yml" \
---from markdown \
---to=pdf \
---output $ClientSubmissionPDFOutputFile
-
-echo "Generating MSWord output for client submission version..."
-
-pandoc \
-"$ClientSubmissionMarkdownOutputFile" \
---metadata-file="../build-temp/ClientSubmission.yml" \
---from markdown \
---to=docx \
---reference-doc=resume-docx-reference.docx \
---output $ClientSubmissionMSWordOutputFile

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,7 +0,0 @@
-Thanks for contributing to b3bp! As part of your PR, have you:
-
-- [ ] Added an item in [CHANGELOG.md](https://github.com/kvz/bash3boilerplate/blob/HEAD/CHANGELOG.md) with attribution?
-- [ ] Added your name to the [README.md](https://github.com/kvz/bash3boilerplate/blob/HEAD/README.md#authors)
-- [ ] Linted your code? (`make test` should do the trick)
-
-If so, great! Feel free to replace this message with a description of your work and hit submit!

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.github/dependabot.yml

@@ -1,5 +0,0 @@
-groups:
-  production-dependencies:
-    dependency-type: 'production'
-  development-dependencies:
-    dependency-type: 'development'

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.github/workflows/ci.yml

@@ -1,30 +0,0 @@
-name: b3bp CI
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    types:
-      - opened
-      - synchronize
-jobs:
-  ci:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-        with:
-          fetch-depth: 1
-      - uses: actions/setup-node@v1
-        with:
-          node-version: 18.x
-      - name: Install
-        run: |
-          corepack yarn
-      - name: Lint
-        env:
-          SHELLCHECK_SEVERITY: warning
-        run: |
-          corepack yarn lint
-      - name: Test
-        run: |
-          corepack yarn test

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.gitignore

@@ -1,5 +0,0 @@
-.yarn
-assets/build
-env.sh
-node_modules
-npm-debug.log

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.shellcheckrc

@@ -1,3 +0,0 @@
-external-sources=true
-shell=bash
-color=always

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.vscode/bash3boilerplate.code-workspace

@@ -1,8 +0,0 @@
-{
-	"folders": [
-		{
-			"path": ".."
-		}
-	],
-	"settings": {}
-}

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.yarnrc.yml

@@ -1 +0,0 @@
-nodeLinker: node-modules

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/CHANGELOG.md

@@ -1,175 +0,0 @@
-# Changelog
-
-Here's is a combined todo/done list. You can see what todos are planned for the upcoming release, as well as ideas that may/may not make into a release in `Ideas`.
-
-## Ideas
-
-Unplanned.
-
-- [ ] Better style guide checking (#84)
-
-## main
-
-Released: TBA.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/2.7.2...main).
-
-- [ ]
-
-## 2.7.2
-
-Released: 2023-08-29
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.4.1...2.7.2).
-
-- [x] Upgrade and cleanup node dependencies
-- [x] Remove lanyon-based website in favor of simple redirect to github for bash3boilerplate.sh
-- [x] Make tests pass again
-- [x] Make linting and style checking separate actions
-- [x] Add feature to edit/update comments in ini file (#132, @rfuehrer)
-- [x] Upgrade to `lanyon@0.1.16`
-- [x] Capture correct error_code in err_report (#124, @eval)
-- [x] Enhanced ini file handling: create new file, create new sections, handle default section, read key from given section (@rfuehrer)
-
-## v2.4.2
-
-Released: 2019-11-07.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.4.1...v2.4.2).
-
-- [x] Upgrade to `lanyon@0.1.16`
-- [x] Capture correct error_code in err_report (#124, @eval)
-- [x] Enhanced ini file handling: create new file, create new sections, handle default section, read key from given section (@rfuehrer)
-
-## v2.4.1
-
-Released: 2019-11-07.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.3.0...v2.4.1).
-
-- [x] Upgrade to `lanyon@0.1.7`
-- [x] Allow counting how many times an argument is used (@genesiscloud)
-- [x] Fix typos in megamount (thanks @gsaponaro)
-- [x] Enable color in screen or tmux (#92, @gmasse)
-- [x] Change `egrep` to `grep -E` in test and lib scripts to comply with ShellCheck (#92, @gmasse)
-- [x] Fix typo in FAQ (#92, @gmasse)
-- [x] Fix Travis CI failure on src/templater.sh (@gmasse)
-- [x] Add magic variable which contains full command invocation
-- [x] More contrasted alert and emergency colors (#111 @gmeral)
-- [x] Add support for repeatable arguments (@genesiscloud)
-- [x] Fix remaining warnings with shellcheck v0.7.0 (#107, @genesiscloud)
-
-## v2.4.0
-
-Released: 2016-12-21.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.3.0...v2.4.0).
-
-- [x] Upgrade to `lanyon@0.0.143`
-
-## v2.3.0
-
-Released: 2016-12-21.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.2.0...v2.3.0).
-
-- [x] Add magic variable `__i_am_main_script` to distinguish if b3bp is being sourced or called directly (#45, @zbeekman)
-- [x] Add style checks for tab characters and trailing whitespace (@zbeekman)
-- [x] Add backtracing to help localize errors (#44, @zbeekman)
-- [x] Additional FAQ entries (#47, suggested by @gdevenyi, implemented by @zbeekman)
-- [x] Ensure that shifting over `--` doesn't throw an errexit error (#21, @zbeekman)
-- [x] Add Pull Request template (#83)
-
-## v2.2.0
-
-Released: 2016-12-21.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.1.0...v2.2.0).
-
-- [x] README and FAQ improvements (#66, @mstreuhofer)
-- [x] Add support for sourcing b3bp (#61, @mstreuhofer)
-- [x] Upgrade all Node.js dependencies for development (#78)
-- [x] Switch to http://lanyon.io for static site building, add a new logo
-- [x] Cleanup environment variables (#58, @mstreuhofer)
-- [x] Support multi-line logs (#57, @mstreuhofer)
-- [x] Run shellcheck as part of the acceptance test (#79, @mstreuhofer)
-- [x] Brace all variables, used `[[` instead of `[` (#33, #76, @mstreuhofer)
-- [x] Add automatic usage validation for required args (#22, #65, @mstreuhofer)
-- [x] Remove all usage of eval (@mstreuhofer)
-- [x] Get rid of awk, sed & egrep usage (#71, @mstreuhofer)
-- [x] Fix auto-color-off code (#69, #70, @mstreuhofer)
-- [x] Use shellcheck to find and fix unclean code (#68, #80, @mstreuhofer)
-- [x] Allow for multiline opt description in `__usage` (#7, @mstreuhofer)
-- [x] Allow `__usage` and `__helptext` to be defined before sourcing `main.sh` thus makeing b3bp behave like a library (@mstreuhofer)
-- [x] Add the same License text to each script header (@mstreuhofer)
-
-## v2.1.0
-
-Released: 2016-11-08.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.0.0...v2.1.0).
-
-- [x] Cleanup b3bp variables (adds prefixes across the board) (thanks @mstreuhofer)
-- [x] Add multi-line logging support (thanks @mstreuhofer)
-- [x] Mangle long-option names to allow dashes (thanks @zbeekman)
-- [x] Remove OS detection altogether (#38, thx @zbeekman)
-- [x] Offer the main template for download as http://bash3boilerplate.sh/main.sh
-- [x] Better OS detection (#38, thx @moviuro)
-- [x] Improve README copy (#34, thx galaktos)
-- [x] Fix unquoted variable access within (#34 thx galaktos)
-- [x] For delete-key-friendliness, bundle the commandline definition block along with its parser
-- [x] Less verbose header comments
-- [x] For delete-key-friendliness, don't crash on undeclared help vars
-- [x] Introduce `errtrace`, which is on by default (BREAKING)
-- [x] Add a configurable `helptext` that is left alone by the parses and allows you to have a richer help
-- [x] Add a simple documentation website
-- [x] Add best practice of using `__double_underscore_prefixed_vars` to indicate global variables that are solely controlled inside your script
-- [x] Make license more permissive by not requiring distribution of the LICENSE file if the copyright & attribution comments are left intact
-- [x] Respect `--no-color` by setting the `NO_COLOR` flag in `main.sh` (#25, thx @gdevenyi)
-- [x] Split out changelog into separate file
-- [x] Added a [FAQ](./FAQ.md) (#15, #14, thanks @rouson)
-- [x] Fix Travis OSX testing (before, it would silently pass failures) (#10)
-- [x] Enable dashes in long, GNU style options, as well as numbers (thanks @zbeekman)
-
-## v2.0.0
-
-Released: 2016-02-17.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.2.1...v2.0.0).
-
-- [x] Add tests for `templater` and follow Library export best practices
-- [x] Add tests for `ini_val` and follow Library export best practices
-- [x] Add tests for `parse_url` and follow Library export best practices
-- [x] Add tests for `megamount` and follow Library export best practices
-- [x] Remove `bump` from `src` (BREAKING)
-- [x] Remove `semver` from `src` (BREAKING)
-
-## v1.2.1
-
-Released: 2016-02-17.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.2.0...v1.2.1).
-
-- [x] Add Travis CI automated testing for OSX (thanks @zbeekman)
-
-## v1.2.0
-
-Released: 2016-02-16.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.1.0...v1.2.0).
-
-- [x] Allow disabling colors via `NO_COLOR` environment variable
-- [x] Enable `errexit`, `nounset` and `pipefail` options at the top of the script already
-- [x] More refined colors (thanks @arathai)
-- [x] Add a changelog to the README
-- [x] Add `__os` magic var (limited to discovering OSX and defaulting to Linux for now)
-- [x] Add `__base` magic var (`main`, if the source script is `main.sh`)
-- [x] Enable long, GNU style options (thanks @zbeekman)
-- [x] Add Travis CI automated testing for Linux
-
-## v1.1.0
-
-Released: 2015-06-29.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.0.3...v1.1.0).
-
-- [x] Add `ALLOW_REMAINDERS` configuration to templater
-- [x] Fix typo: 'debugmdoe' to 'debugmode' (thanks @jokajak)
-- [x] Use `${BASH_SOURCE[0]}` for `__file` instead of `${0}`
-
-## v1.0.3
-
-Released: 2014-11-02.
-[Diff](https://github.com/kvz/bash3boilerplate/compare/5db569125319a89b9561b434db84e4d91faefb63...v1.0.3).
-
-- [x] Add `ini_val`, `megamount`, `parse_url`
-- [x] Add re-usable libraries in `./src`
-- [x] Use npm as an additional distribution channel

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/FAQ.md

@@ -1,171 +0,0 @@
-[This document is formatted with GitHub-Flavored Markdown. ]: #
-[For better viewing, including hyperlinks, read it online at ]: #
-[https://github.com/kvz/bash3boilerplate/blob/HEAD/FAQ.md ]: #
-
-## Contents
-
-- [What is a CLI](#what-is-a-cli)?
-- [How do I incorporate BASH3 Boilerplate into my own project](#how-do-i-incorporate-bash3-boilerplate-into-my-own-project)?
-- [How do I add a command-line flag](#how-do-i-add-a-command-line-flag)?
-- [How do I access the value of a command-line argument](#how-do-i-access-the-value-of-a-command-line-argument)?
-- [What is a magic variable](#what-is-a-magic-variable)?
-- [How do I submit an issue report](#how-do-i-submit-an-issue-report)?
-- [How can I contribute to this project](#how-can-i-contribute-to-this-project)?
-- [Why are you typing BASH in all caps](#why-are-you-typing-bash-in-all-caps)?
-- [You are saying you are portable, but why won't b3bp code run in dash / busybox / posh / ksh / mksh / zsh](#you-are-saying-you-are-portable-but-why-wont-b3bp-code-run-in-dash--busybox--posh--ksh--mksh--zsh)?
-- [How do I do Operating System detection](#how-do-i-do-operating-system-detection)?
-- [How do I access a potentially unset (environment) variable](#how-do-i-access-a-potentially-unset-environment-variable)?
-- [How can I detect or trap CTRL-C and other signals](#how-can-i-detect-or-trap-ctrl-c-and-other-signals)?
-- [How can I get the PID of my running script](how-can-i-get-the-pid-of-my-running-script)?
-
-<!--more-->
-
-# Frequently Asked Questions
-
-## What is a CLI?
-
-A "CLI" is a [command-line interface](https://en.wikipedia.org/wiki/Command-line_interface).
-
-## How do I incorporate BASH3 Boilerplate into my own project?
-
-You can incorporate BASH3 Boilerplate into your project in one of two ways:
-
-1. Copy the desired portions of [`main.sh`](http://bash3boilerplate.sh/main.sh) into your own script.
-1. Download [`main.sh`](http://bash3boilerplate.sh/main.sh) and start pressing the delete-key to remove unwanted things
-
-Once the `main.sh` has been tailor-made for your project, you can either append your own script in the same file, or source it in the following ways:
-
-1. Copy [`main.sh`](http://bash3boilerplate.sh/main.sh) into the same directory as your script and then edit and embed it into your script using Bash's `source` include feature, e.g.:
-
-```bash
-#!/usr/bin/env bash
-source main.sh
-```
-
-1. Source [`main.sh`](http://bash3boilerplate.sh/main.sh) in your script or at the command line:
-
-```bash
-#!/usr/bin/env bash
-source main.sh
-```
-
-## How do I add a command-line flag?
-
-1. Copy the line from the `main.sh` [read block](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L109-L115) that most resembles the desired behavior and paste the line into the same block.
-1. Edit the single-character (e.g., `-d`) and, if present, the multi-character (e.g., `--debug`) versions of the flag in the copied line.
-1. Omit the `[arg]` text in the copied line, if the desired flag takes no arguments.
-1. Omit or edit the text after `Default=` to set or not set default values, respectively.
-1. Omit the `Required.` text, if the flag is optional.
-
-## How do I access the value of a command-line argument?
-
-To find out the value of an argument, append the corresponding single-character flag to the text `$arg_`. For example, if the [read block]
-contains the line
-
-```bash
-   -t --temp  [arg] Location of tempfile. Default="/tmp/bar"
-```
-
-then you can evaluate the corresponding argument and assign it to a variable as follows:
-
-```bash
-__temp_file_name="${arg_t}"
-```
-
-## What is a magic variable?
-
-The [magic variables](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L26-L28) in `main.sh` are special in that they have a different value, depending on your environment. You can use `${__file}` to get a reference to your current script, and `${__dir}` to get a reference to the directory it lives in. This is not to be confused with the location of the calling script that might be sourcing the `${__file}`, which is accessible via `${0}`, or the current directory of the administrator running the script, accessible via `$(pwd)`.
-
-## How do I submit an issue report?
-
-Please visit our [Issues](https://github.com/kvz/bash3boilerplate/issues) page.
-
-## How can I contribute to this project?
-
-Please fork this repository. After that, create a branch containing your suggested changes and submit a pull request based on the main branch
-of <https://github.com/kvz/bash3boilerplate/>. We are always more than happy to accept your contributions!
-
-## Why are you typing BASH in all caps?
-
-As an acronym, Bash stands for Bourne-again shell, and is usually written with one uppercase.
-This project's name, however, is "BASH3 Boilerplate". It is a reference to
-"[HTML5 Boilerplate](https://html5boilerplate.com/)", which was founded to serve a similar purpose,
-only for crafting webpages.
-Somewhat inconsistent – but true to Unix ancestry – the abbreviation for our project is "b3bp".
-
-## You are saying you are portable, but why won't b3bp code run in dash / busybox / posh / ksh / mksh / zsh?
-
-When we say _portable_, we mean across Bash versions. Bash is widespread and most systems
-offer at least version 3 of it. Make sure you have that available and b3bp will work for you.
-
-We run automated tests to make sure that it will. Here is some proof for the following platforms:
-
-- [Linux](https://travis-ci.org/kvz/bash3boilerplate/jobs/109804166#L91-L94) `GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)`
-- [OSX](https://travis-ci.org/kvz/bash3boilerplate/jobs/109804167#L2453-L2455) `GNU bash, version 3.2.51(1)-release (x86_64-apple-darwin13)`
-
-This portability, however, does not mean that we try to be compatible with
-KornShell, Zsh, posh, yash, dash, or other shells. We allow syntax that would explode if
-you pasted it in anything but Bash 3 and up.
-
-## How do I do Operating System detection?
-
-We used to offer a magic `__os` variable, but we quickly [discovered](https://github.com/kvz/bash3boilerplate/issues/38) that it would be hard
-to create a satisfactory abstraction that is not only correct, but also covers enough use-cases,
-while still having a relatively small footprint in `main.sh`.
-
-For simple OS detection, we recommend using the `${OSTYPE}` variable available in Bash as
-is demoed in [this stackoverflow post](http://stackoverflow.com/a/8597411/151666):
-
-```bash
-if [[ "${OSTYPE}" = "linux-gnu" ]]; then
-  echo "GNU Linux"
-elif [[ "${OSTYPE}" = "darwin"* ]]; then
-  echo "Mac OSX"
-elif [[ "${OSTYPE}" = "cygwin" ]]; then
-  echo "POSIX compatibility layer and Linux environment emulation for Windows"
-elif [[ "${OSTYPE}" = "msys" ]]; then
-  echo "Lightweight shell and GNU utilities compiled for Windows (part of MinGW)"
-elif [[ "${OSTYPE}" = "win32" ]]; then
-  echo "I'm not sure this can happen."
-elif [[ "${OSTYPE}" = "freebsd"* ]]; then
-  echo "..."
-else
-  echo "Unknown."
-fi
-```
-
-## How do I access a potentially unset (environment) variable?
-
-The set -o nounset line in `main.sh` causes error termination when an unset environment variables is detected as unbound. There are multiple ways to avoid this.
-
-Some code to illustrate:
-
-```bash
-# method 1
-echo ${NAME1:-Damian} # echos Damian, $NAME1 is still unset
-# method 2
-echo ${NAME2:=Damian} # echos Damian, $NAME2 is set to Damian
-# method 3
-NAME3=${NAME3:-Damian}; echo ${NAME3} # echos Damian, $NAME3 is set to Damian
-```
-
-This subject is briefly touched on as well in the [Safety and Portability section under point 5](README.md#safety-and-portability). b3bp currently uses [method 1](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L252) when we want to access a variable that could be undeclared, and [method 3](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L31) when we also want to set a default to an undeclared variable, because we feel it is more readable than method 2. We feel `:=` is easily overlooked, and not very beginner friendly. Method 3 seems more explicit in that regard in our humble opinion.
-
-## How can I detect or trap Ctrl-C and other signals?
-
-You can trap [Unix signals](https://en.wikipedia.org/wiki/Unix_signal) like [Ctrl-C](https://en.wikipedia.org/wiki/Control-C) with code similar to:
-
-```bash
-# trap ctrl-c and call ctrl_c()
-trap ctrl_c INT
-
-function ctrl_c() {
-        echo "** Trapped CTRL-C"
-}
-```
-
-See http://mywiki.wooledge.org/SignalTrap for a list of signals, examples, and an in depth discussion.
-
-## How can I get the PID of my running script?
-
-The PID of a running script is contained in the `${$}` variable. This is _not_ the pid of any subshells. With Bash 4 you can get the PID of your subshell with `${BASHPID}`. For a comprehensive list of Bash built in variables see, e.g., http://www.tldp.org/LDP/abs/html/internalvariables.html

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2013 Kevin van Zonneveld and contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/Makefile

@@ -1,59 +0,0 @@
-# Licensed under MIT.
-# Copyright (2016) by Kevin van Zonneveld https://twitter.com/kvz
-#
-# https://www.npmjs.com/package/fakefile
-#
-# Please do not edit this file directly, but propose changed upstream instead:
-# https://github.com/kvz/fakefile/blob/main/Makefile
-#
-# This Makefile offers convience shortcuts into any Node.js project that utilizes npm scripts.
-# It functions as a wrapper around the actual listed in `package.json`
-# So instead of typing:
-#
-#  $ npm script build:assets
-#
-# you could also type:
-#
-#  $ make build-assets
-#
-# Notice that colons (:) are replaced by dashes for Makefile compatibility.
-#
-# The benefits of this wrapper are:
-#
-# - You get to keep the the scripts package.json, which is more portable
-#   (Makefiles & Windows are harder to mix)
-# - Offer a polite way into the project for developers coming from different
-#   languages (npm scripts is obviously very Node centric)
-# - Profit from better autocomplete (make <TAB><TAB>) than npm currently offers.
-#   OSX users will have to install bash-completion
-#   (http://davidalger.com/development/bash-completion-on-os-x-with-brew/)
-
-ifeq ($(shell test -e ./yarn.lock && echo -n yes),yes)
-	RUNNER=yarn
-	INSTALLER=yarn install
-else
-	RUNNER=npm run
-	INSTALLER=npm install
-endif
-
-define npm_script_targets
-TARGETS := $(shell \
-	node -e 'for (var k in require("./package.json").scripts) {console.log(k.replace(/:/g, "-"));}'
-		| grep -v -E "^install$$"
-)
-$$(TARGETS):
-	$(RUNNER) $(shell \
-							node -e 'for (var k in require("./package.json").scripts) {console.log(k.replace(/:/g, "-"), k);}'
-								| grep -E "^$(MAKECMDGOALS)\s"
-								| head -n1
-								| awk '{print $$2}'
-							)
-
-.PHONY: $$(TARGETS)
-endef
-
-$(eval $(call npm_script_targets))
-
-# These npm run scripts are available, without needing to be mentioned in `package.json`
-install:
-	$(INSTALLER)

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/README.md

@@ -1,175 +0,0 @@
-[This document is formatted with GitHub-Flavored Markdown. ]: #
-[For better viewing, including hyperlinks, read it online at ]: #
-[https://github.com/kvz/bash3boilerplate/blob/HEAD/README.md]: #
-
-- [Overview](#overview)
-- [Goals](#goals)
-- [Features](#features)
-- [Installation](#installation)
-- [Changelog](#changelog)
-- [Frequently Asked Questions](#frequently-asked-questions)
-- [Best Practices](#best-practices)
-- [Who uses b3bp](#who-uses-b3bp)
-- [Authors](#authors)
-- [License](#license)
-
-## Overview
-
-<!--more-->
-
-When hacking up Bash scripts, there are often things such as logging or command-line argument parsing that:
-
-- You need every time
-- Come with a number of pitfalls you want to avoid
-- Keep you from your actual work
-
-Here's an attempt to bundle those things in a generalized way so that
-they are reusable as-is in most scripts.
-
-We call it "BASH3 Boilerplate" or b3bp for short.
-
-## Goals
-
-Delete-Key-**Friendly**. Instead of introducing packages, includes, compilers, etc., we propose using [`main.sh`](https://bash3boilerplate.sh/main.sh) as a base and removing the parts you don't need.
-While this may feel a bit archaic at first, it is exactly the strength of Bash scripts that we should want to embrace.
-
-**Portable**. We are targeting Bash 3 (OSX still ships
-with 3, for instance). If you are going to ask people to install
-Bash 4 first, you might as well pick a more advanced language as a
-dependency.
-
-## Features
-
-- Conventions that will make sure that all your scripts follow the same, battle-tested structure
-- Safe by default (break on error, pipefail, etc.)
-- Configuration by environment variables
-- Simple command-line argument parsing that requires no external dependencies. Definitions are parsed from help info, ensuring there will be no duplication
-- Helpful magic variables like `__file` and `__dir`
-- Logging that supports colors and is compatible with [Syslog Severity levels](https://en.wikipedia.org/wiki/Syslog#Severity_levels), as well as the [twelve-factor](https://12factor.net/) guidelines
-
-## Installation
-
-There are three different ways to install b3bp:
-
-### Option 1: Download the main template
-
-Use curl or wget to download the source and save it as your script. Then you can start deleting the unwanted bits, and adding your own logic.
-
-```bash
-wget https://bash3boilerplate.sh/main.sh
-vim main.sh
-```
-
-### Option 2: Clone the entire project
-
-Besides `main.sh`, this will also get you the entire b3bp repository. This includes a few extra functions that we keep in the `./src` directory.
-
-```bash
-git clone git@github.com:kvz/bash3boilerplate.git
-```
-
-### Option 3: Require via npm
-
-As of `v1.0.3`, b3bp can also be installed as a Node module, meaning you can define it as a dependency in `package.json` via:
-
-```bash
-npm init
-npm install --save --save-exact bash3boilerplate
-```
-
-Even though this option introduces a Node.js dependency, it does allow for easy version pinning and distribution in environments that already have this prerequisite. This is, however, entirely optional and nothing prevents you from ignoring this possibility.
-
-## Changelog
-
-Please see the [CHANGELOG.md](./CHANGELOG.md) file.
-
-## Frequently Asked Questions
-
-Please see the [FAQ.md](./FAQ.md) file.
-
-## Best practices
-
-As of `v1.0.3`, b3bp offers some nice re-usable libraries in `./src`. In order to make the snippets in `./src` more useful, we recommend the following guidelines.
-
-### Function packaging
-
-It is nice to have a Bash package that can not only be used in the terminal, but also invoked as a command line function. In order to achieve this, the exporting of your functionality _should_ follow this pattern:
-
-```bash
-if [[ "${BASH_SOURCE[0]}" = "${0}" ]]; then
-  my_script "${@}"
-  exit $?
-fi
-export -f my_script
-```
-
-This allows a user to `source` your script or invoke it as a script.
-
-```bash
-# Running as a script
-$ ./my_script.sh some args --blah
-# Sourcing the script
-$ source my_script.sh
-$ my_script some more args --blah
-```
-
-(taken from the [bpkg](https://raw.githubusercontent.com/bpkg/bpkg/HEAD/README.md) project)
-
-### Scoping
-
-1. In functions, use `local` before every variable declaration.
-1. Use `UPPERCASE_VARS` to indicate environment variables that can be controlled outside your script.
-1. Use `__double_underscore_prefixed_vars` to indicate global variables that are solely controlled inside your script, with the exception of arguments that are already prefixed with `arg_`, as well as functions, over which b3bp poses no restrictions.
-
-### Coding style
-
-1. Use two spaces for tabs, do not use tab characters.
-1. Do not introduce whitespace at the end of lines or on blank lines as they obfuscate version control diffs.
-1. Use long options (`logger --priority` vs `logger -p`). If you are on the CLI, abbreviations make sense for efficiency. Nevertheless, when you are writing reusable scripts, a few extra keystrokes will pay off in readability and avoid ventures into man pages in the future, either by you or your collaborators. Similarly, we prefer `set -o nounset` over `set -u`.
-1. Use a single equal sign when checking `if [[ "${NAME}" = "Kevin" ]]`; double or triple signs are not needed.
-1. Use the new bash builtin test operator (`[[ ... ]]`) rather than the old single square bracket test operator or explicit call to `test`.
-
-### Safety and Portability
-
-1. Use `{}` to enclose your variables. Otherwise, Bash will try to access the `$ENVIRONMENT_app` variable in `/srv/$ENVIRONMENT_app`, whereas you probably intended `/srv/${ENVIRONMENT}_app`. Since it is easy to miss cases like this, we recommend that you make enclosing a habit.
-1. Use `set`, rather than relying on a shebang like `#!/usr/bin/env bash -e`, since that is neutralized when someone runs your script as `bash yourscript.sh`.
-1. Use `#!/usr/bin/env bash`, as it is more portable than `#!/bin/bash`.
-1. Use `${BASH_SOURCE[0]}` if you refer to current file, even if it is sourced by a parent script. In other cases, use `${0}`.
-1. Use `:-` if you want to test variables that could be undeclared. For instance, with `if [[ "${NAME:-}" = "Kevin" ]]`, `$NAME` will evaluate to `Kevin` if the variable is empty. The variable itself will remain unchanged. The syntax to assign a default value is `${NAME:=Kevin}`.
-
-## Who uses b3bp?
-
-- [Transloadit](https://transloadit.com)
-- [OpenCoarrays](https://www.opencoarrays.org)
-- [Sourcery Institute](https://www.sourceryinstitute.org)
-- [Computational Brain Anatomy Laboratory](https://cobralab.ca/)
-- [Genesis Cloud](https://genesiscloud.com/)
-
-We are looking for endorsements! Are you also using b3bp? [Let us know](https://github.com/kvz/bash3boilerplate/issues/new?title=I%20use%20b3bp) and get listed.
-
-## Authors
-
-- [Kevin van Zonneveld](https://kvz.io)
-- [Izaak Beekman](https://izaakbeekman.com/)
-- [Manuel Streuhofer](https://github.com/mstreuhofer)
-- [Alexander Rathai](mailto:Alexander.Rathai@gmail.com)
-- [Dr. Damian Rouson](https://www.sourceryinstitute.org/) (documentation, feedback)
-- [@jokajak](https://github.com/jokajak) (documentation)
-- [Gabriel A. Devenyi](https://staticwave.ca/) (feedback)
-- [@bravo-kernel](https://github.com/bravo-kernel) (feedback)
-- [@skanga](https://github.com/skanga) (feedback)
-- [galaktos](https://www.reddit.com/user/galaktos) (feedback)
-- [@moviuro](https://github.com/moviuro) (feedback)
-- [Giovanni Saponaro](https://github.com/gsaponaro) (feedback)
-- [Germain Masse](https://github.com/gmasse)
-- [A. G. Madi](https://github.com/warpengineer)
-- [Lukas Stockner](mailto:oss@genesiscloud.com)
-- [Gert Goet](https://github.com/eval)
-- [@rfuehrer](https://github.com/rfuehrer)
-
-## License
-
-Copyright (c) 2013 Kevin van Zonneveld and [contributors](https://github.com/kvz/bash3boilerplate#authors).
-Licensed under [MIT](https://raw.githubusercontent.com/kvz/bash3boilerplate/HEAD/LICENSE).
-You are not obligated to bundle the LICENSE file with your b3bp projects as long
-as you leave these references intact in the header comments of your source files.

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/docs/CNAME

@@ -1 +0,0 @@
-bash3boilerplate.sh

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/docs/index.html

@@ -1,15 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta
-      http-equiv="refresh"
-      content="0;url=https://github.com/kvz/bash3boilerplate"
-    />
-    <title>Redirecting...</title>
-  </head>
-  <body>
-    If you are not redirected,
-    <a href="https://github.com/kvz/bash3boilerplate">click here</a>.
-  </body>
-</html>

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/example.sh

@@ -1,147 +0,0 @@
-#!/usr/bin/env bash
-# This file:
-#
-#  - Demos BASH3 Boilerplate (change this for your script)
-#
-# Usage:
-#
-#  LOG_LEVEL=7 ./example.sh -f /tmp/x -d (change this for your script)
-#
-# Based on a template by BASH3 Boilerplate v2.3.0
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-
-### BASH3 Boilerplate (b3bp) Header
-##############################################################################
-
-# Commandline options. This defines the usage page, and is used to parse cli
-# opts & defaults from. The parsing is unforgiving so be precise in your syntax
-# - A short option must be preset for every long option; but every short option
-#   need not have a long option
-# - `--` is respected as the separator between options and arguments
-# - We do not bash-expand defaults, so setting '~/app' as a default will not resolve to ${HOME}.
-#   you can use bash variables to work around this (so use ${HOME} instead)
-
-# shellcheck disable=SC2034
-read -r -d '' __usage <<-'EOF' || true # exits non-zero when EOF encountered
-  -f --file  [arg] Filename to process. Required.
-  -t --temp  [arg] Location of tempfile. Default="/tmp/bar"
-  -v               Enable verbose mode, print script as it is executed
-  -d --debug       Enables debug mode
-  -h --help        This page
-  -n --no-color    Disable color output
-  -1 --one         Do just one thing
-  -i --input [arg] File to process. Can be repeated.
-  -x               Specify a flag. Can be repeated.
-EOF
-
-# shellcheck disable=SC2034
-read -r -d '' __helptext <<-'EOF' || true # exits non-zero when EOF encountered
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-EOF
-
-# shellcheck source=main.sh
-source "$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/main.sh"
-
-
-### Signal trapping and backtracing
-##############################################################################
-
-function __b3bp_cleanup_before_exit () {
-  info "Cleaning up. Done"
-}
-trap __b3bp_cleanup_before_exit EXIT
-
-# requires `set -o errtrace`
-__b3bp_err_report() {
-    local error_code=${?}
-    # shellcheck disable=SC2154
-    error "Error in ${__file} in function ${1} on line ${2}"
-    exit ${error_code}
-}
-# Uncomment the following line for always providing an error backtrace
-# trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
-
-
-### Command-line argument switches (like -d for debugmode, -h for showing helppage)
-##############################################################################
-
-# debug mode
-if [[ "${arg_d:?}" = "1" ]]; then
-  set -o xtrace
-  PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
-  LOG_LEVEL="7"
-  # Enable error backtracing
-  trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
-fi
-
-# verbose mode
-if [[ "${arg_v:?}" = "1" ]]; then
-  set -o verbose
-fi
-
-# no color mode
-if [[ "${arg_n:?}" = "1" ]]; then
-  NO_COLOR="true"
-fi
-
-# help mode
-if [[ "${arg_h:?}" = "1" ]]; then
-  # Help exists with code 1
-  help "Help using ${0}"
-fi
-
-
-### Validation. Error out if the things required for your script are not present
-##############################################################################
-
-[[ "${arg_f:-}" ]]     || help      "Setting a filename with -f or --file is required"
-[[ "${LOG_LEVEL:-}" ]] || emergency "Cannot continue without LOG_LEVEL. "
-
-
-### Runtime
-##############################################################################
-
-# shellcheck disable=SC2154
-info "__i_am_main_script: ${__i_am_main_script}"
-# shellcheck disable=SC2154
-info "__file: ${__file}"
-# shellcheck disable=SC2154
-info "__dir: ${__dir}"
-# shellcheck disable=SC2154
-info "__base: ${__base}"
-info "OSTYPE: ${OSTYPE}"
-
-info "arg_f: ${arg_f}"
-info "arg_d: ${arg_d}"
-info "arg_v: ${arg_v}"
-info "arg_h: ${arg_h}"
-if [[ -n "${arg_i:-}" ]]; then
-  info "arg_i: ${#arg_i[@]}"
-  for input_file in "${arg_i[@]}"; do
-    info " - ${input_file}"
-  done
-else
-  info "arg_i: 0"
-fi
-# shellcheck disable=SC2015
-[[ -n "${arg_x:-}" ]] && info "arg_x: ${#arg_x[@]}" || info "arg_x: 0"
-
-info "$(echo -e "multiple lines example - line #1\\nmultiple lines example - line #2\\nimagine logging the output of 'ls -al /path/'")"
-
-# All of these go to STDERR, so you can use STDOUT for piping machine readable information to other software
-debug "Info useful to developers for debugging the application, not useful during operations."
-info "Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required."
-notice "Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required."
-warning "Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time."
-error "Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time."
-critical "Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection."
-alert "Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection."
-emergency "A \"panic\" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call."

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/main.sh

@@ -1,453 +0,0 @@
-#!/usr/bin/env bash
-# This file:
-#
-#  - Demos BASH3 Boilerplate (change this for your script)
-#
-# Usage:
-#
-#  LOG_LEVEL=7 ./main.sh -f /tmp/x -d (change this for your script)
-#
-# Based on a template by BASH3 Boilerplate vv2.7.2
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-# Exit on error. Append "|| true" if you expect an error.
-set -o errexit
-# Exit on error inside any functions or subshells.
-set -o errtrace
-# Do not allow use of undefined vars. Use ${VAR:-} to use an undefined VAR
-set -o nounset
-# Catch the error in case mysqldump fails (but gzip succeeds) in `mysqldump |gzip`
-set -o pipefail
-# Turn on traces, useful while debugging but commented out by default
-# set -o xtrace
-
-if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
-  __i_am_main_script="0" # false
-
-  if [[ "${__usage+x}" ]]; then
-    if [[ "${BASH_SOURCE[1]}" = "${0}" ]]; then
-      __i_am_main_script="1" # true
-    fi
-
-    __b3bp_external_usage="true"
-    __b3bp_tmp_source_idx=1
-  fi
-else
-  __i_am_main_script="1" # true
-  [[ "${__usage+x}" ]] && unset -v __usage
-  [[ "${__helptext+x}" ]] && unset -v __helptext
-fi
-
-# Set magic variables for current file, directory, os, etc.
-__dir="$(cd "$(dirname "${BASH_SOURCE[${__b3bp_tmp_source_idx:-0}]}")" && pwd)"
-__file="${__dir}/$(basename "${BASH_SOURCE[${__b3bp_tmp_source_idx:-0}]}")"
-__base="$(basename "${__file}" .sh)"
-# shellcheck disable=SC2034,SC2015
-__invocation="$(printf %q "${__file}")$( (($#)) && printf ' %q' "$@" || true)"
-
-# Define the environment variables (and their defaults) that this script depends on
-LOG_LEVEL="${LOG_LEVEL:-6}" # 7 = debug -> 0 = emergency
-NO_COLOR="${NO_COLOR:-}"    # true = disable color. otherwise autodetected
-
-
-### Functions
-##############################################################################
-
-function __b3bp_log () {
-  local log_level="${1}"
-  shift
-
-  # shellcheck disable=SC2034
-  local color_debug="\\x1b[35m"
-  # shellcheck disable=SC2034
-  local color_info="\\x1b[32m"
-  # shellcheck disable=SC2034
-  local color_notice="\\x1b[34m"
-  # shellcheck disable=SC2034
-  local color_warning="\\x1b[33m"
-  # shellcheck disable=SC2034
-  local color_error="\\x1b[31m"
-  # shellcheck disable=SC2034
-  local color_critical="\\x1b[1;31m"
-  # shellcheck disable=SC2034
-  local color_alert="\\x1b[1;37;41m"
-  # shellcheck disable=SC2034
-  local color_emergency="\\x1b[1;4;5;37;41m"
-
-  local colorvar="color_${log_level}"
-
-  local color="${!colorvar:-${color_error}}"
-  local color_reset="\\x1b[0m"
-
-  if [[ "${NO_COLOR:-}" = "true" ]] || { [[ "${TERM:-}" != "xterm"* ]] && [[ "${TERM:-}" != "screen"* ]]; } || [[ ! -t 2 ]]; then
-    if [[ "${NO_COLOR:-}" != "false" ]]; then
-      # Don't use colors on pipes or non-recognized terminals
-      color=""; color_reset=""
-    fi
-  fi
-
-  # all remaining arguments are to be printed
-  local log_line=""
-
-  while IFS=$'\n' read -r log_line; do
-    echo -e "$(date -u +"%Y-%m-%d %H:%M:%S UTC") ${color}$(printf "[%9s]" "${log_level}")${color_reset} ${log_line}" 1>&2
-  done <<< "${@:-}"
-}
-
-function emergency () {                                __b3bp_log emergency "${@}"; exit 1; }
-function alert ()     { [[ "${LOG_LEVEL:-0}" -ge 1 ]] && __b3bp_log alert "${@}"; true; }
-function critical ()  { [[ "${LOG_LEVEL:-0}" -ge 2 ]] && __b3bp_log critical "${@}"; true; }
-function error ()     { [[ "${LOG_LEVEL:-0}" -ge 3 ]] && __b3bp_log error "${@}"; true; }
-function warning ()   { [[ "${LOG_LEVEL:-0}" -ge 4 ]] && __b3bp_log warning "${@}"; true; }
-function notice ()    { [[ "${LOG_LEVEL:-0}" -ge 5 ]] && __b3bp_log notice "${@}"; true; }
-function info ()      { [[ "${LOG_LEVEL:-0}" -ge 6 ]] && __b3bp_log info "${@}"; true; }
-function debug ()     { [[ "${LOG_LEVEL:-0}" -ge 7 ]] && __b3bp_log debug "${@}"; true; }
-
-function help () {
-  echo "" 1>&2
-  echo " ${*}" 1>&2
-  echo "" 1>&2
-  echo "  ${__usage:-No usage available}" 1>&2
-  echo "" 1>&2
-
-  if [[ "${__helptext:-}" ]]; then
-    echo " ${__helptext}" 1>&2
-    echo "" 1>&2
-  fi
-
-  exit 1
-}
-
-
-### Parse commandline options
-##############################################################################
-
-# Commandline options. This defines the usage page, and is used to parse cli
-# opts & defaults from. The parsing is unforgiving so be precise in your syntax
-# - A short option must be preset for every long option; but every short option
-#   need not have a long option
-# - `--` is respected as the separator between options and arguments
-# - We do not bash-expand defaults, so setting '~/app' as a default will not resolve to ${HOME}.
-#   you can use bash variables to work around this (so use ${HOME} instead)
-
-# shellcheck disable=SC2015
-[[ "${__usage+x}" ]] || read -r -d '' __usage <<-'EOF' || true # exits non-zero when EOF encountered
-  -f --file  [arg] Filename to process. Required.
-  -t --temp  [arg] Location of tempfile. Default="/tmp/bar"
-  -v               Enable verbose mode, print script as it is executed
-  -d --debug       Enables debug mode
-  -h --help        This page
-  -n --no-color    Disable color output
-  -1 --one         Do just one thing
-  -i --input [arg] File to process. Can be repeated.
-  -x               Specify a flag. Can be repeated.
-EOF
-
-# shellcheck disable=SC2015
-[[ "${__helptext+x}" ]] || read -r -d '' __helptext <<-'EOF' || true # exits non-zero when EOF encountered
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-EOF
-
-# Translate usage string -> getopts arguments, and set $arg_<flag> defaults
-while read -r __b3bp_tmp_line; do
-  if [[ "${__b3bp_tmp_line}" =~ ^- ]]; then
-    # fetch single character version of option string
-    __b3bp_tmp_opt="${__b3bp_tmp_line%% *}"
-    __b3bp_tmp_opt="${__b3bp_tmp_opt:1}"
-
-    # fetch long version if present
-    __b3bp_tmp_long_opt=""
-
-    if [[ "${__b3bp_tmp_line}" = *"--"* ]]; then
-      __b3bp_tmp_long_opt="${__b3bp_tmp_line#*--}"
-      __b3bp_tmp_long_opt="${__b3bp_tmp_long_opt%% *}"
-    fi
-
-    # map opt long name to+from opt short name
-    printf -v "__b3bp_tmp_opt_long2short_${__b3bp_tmp_long_opt//-/_}" '%s' "${__b3bp_tmp_opt}"
-    printf -v "__b3bp_tmp_opt_short2long_${__b3bp_tmp_opt}" '%s' "${__b3bp_tmp_long_opt//-/_}"
-
-    # check if option takes an argument
-    if [[ "${__b3bp_tmp_line}" =~ \[.*\] ]]; then
-      __b3bp_tmp_opt="${__b3bp_tmp_opt}:" # add : if opt has arg
-      __b3bp_tmp_init=""  # it has an arg. init with ""
-      printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "1"
-    elif [[ "${__b3bp_tmp_line}" =~ \{.*\} ]]; then
-      __b3bp_tmp_opt="${__b3bp_tmp_opt}:" # add : if opt has arg
-      __b3bp_tmp_init=""  # it has an arg. init with ""
-      # remember that this option requires an argument
-      printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "2"
-    else
-      __b3bp_tmp_init="0" # it's a flag. init with 0
-      printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "0"
-    fi
-    __b3bp_tmp_opts="${__b3bp_tmp_opts:-}${__b3bp_tmp_opt}"
-
-    if [[ "${__b3bp_tmp_line}" =~ ^Can\ be\ repeated\. ]] || [[ "${__b3bp_tmp_line}" =~ \.\ *Can\ be\ repeated\. ]]; then
-      # remember that this option can be repeated
-      printf -v "__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}" '%s' "1"
-    else
-      printf -v "__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}" '%s' "0"
-    fi
-  fi
-
-  [[ "${__b3bp_tmp_opt:-}" ]] || continue
-
-  if [[ "${__b3bp_tmp_line}" =~ ^Default= ]] || [[ "${__b3bp_tmp_line}" =~ \.\ *Default= ]]; then
-    # ignore default value if option does not have an argument
-    __b3bp_tmp_varname="__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}"
-    if [[ "${!__b3bp_tmp_varname}" != "0" ]]; then
-      # take default
-      __b3bp_tmp_init="${__b3bp_tmp_line##*Default=}"
-      # strip double quotes from default argument
-      __b3bp_tmp_re='^"(.*)"$'
-      if [[ "${__b3bp_tmp_init}" =~ ${__b3bp_tmp_re} ]]; then
-        __b3bp_tmp_init="${BASH_REMATCH[1]}"
-      else
-        # strip single quotes from default argument
-        __b3bp_tmp_re="^'(.*)'$"
-        if [[ "${__b3bp_tmp_init}" =~ ${__b3bp_tmp_re} ]]; then
-          __b3bp_tmp_init="${BASH_REMATCH[1]}"
-        fi
-      fi
-    fi
-  fi
-
-  if [[ "${__b3bp_tmp_line}" =~ ^Required\. ]] || [[ "${__b3bp_tmp_line}" =~ \.\ *Required\. ]]; then
-    # remember that this option requires an argument
-    printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "2"
-  fi
-
-  # Init var with value unless it is an array / a repeatable
-  __b3bp_tmp_varname="__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}"
-  [[ "${!__b3bp_tmp_varname}" = "0" ]] && printf -v "arg_${__b3bp_tmp_opt:0:1}" '%s' "${__b3bp_tmp_init}"
-done <<< "${__usage:-}"
-
-# run getopts only if options were specified in __usage
-if [[ "${__b3bp_tmp_opts:-}" ]]; then
-  # Allow long options like --this
-  __b3bp_tmp_opts="${__b3bp_tmp_opts}-:"
-
-  # Reset in case getopts has been used previously in the shell.
-  OPTIND=1
-
-  # start parsing command line
-  set +o nounset # unexpected arguments will cause unbound variables
-                 # to be dereferenced
-  # Overwrite $arg_<flag> defaults with the actual CLI options
-  while getopts "${__b3bp_tmp_opts}" __b3bp_tmp_opt; do
-    [[ "${__b3bp_tmp_opt}" = "?" ]] && help "Invalid use of script: ${*} "
-
-    if [[ "${__b3bp_tmp_opt}" = "-" ]]; then
-      # OPTARG is long-option-name or long-option=value
-      if [[ "${OPTARG}" =~ .*=.* ]]; then
-        # --key=value format
-        __b3bp_tmp_long_opt=${OPTARG/=*/}
-        # Set opt to the short option corresponding to the long option
-        __b3bp_tmp_varname="__b3bp_tmp_opt_long2short_${__b3bp_tmp_long_opt//-/_}"
-        printf -v "__b3bp_tmp_opt" '%s' "${!__b3bp_tmp_varname}"
-        OPTARG=${OPTARG#*=}
-      else
-        # --key value format
-        # Map long name to short version of option
-        __b3bp_tmp_varname="__b3bp_tmp_opt_long2short_${OPTARG//-/_}"
-        printf -v "__b3bp_tmp_opt" '%s' "${!__b3bp_tmp_varname}"
-        # Only assign OPTARG if option takes an argument
-        __b3bp_tmp_varname="__b3bp_tmp_has_arg_${__b3bp_tmp_opt}"
-        __b3bp_tmp_varvalue="${!__b3bp_tmp_varname}"
-        [[ "${__b3bp_tmp_varvalue}" != "0" ]] && __b3bp_tmp_varvalue="1"
-        printf -v "OPTARG" '%s' "${@:OPTIND:${__b3bp_tmp_varvalue}}"
-        # shift over the argument if argument is expected
-        ((OPTIND+=__b3bp_tmp_varvalue))
-      fi
-      # we have set opt/OPTARG to the short value and the argument as OPTARG if it exists
-    fi
-
-    __b3bp_tmp_value="${OPTARG}"
-
-    __b3bp_tmp_varname="__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}"
-    if [[ "${!__b3bp_tmp_varname}" != "0" ]]; then
-      # repeatables
-      # shellcheck disable=SC2016
-      if [[ -z "${OPTARG}" ]]; then
-        # repeatable flags, they increcemnt
-        __b3bp_tmp_varname="arg_${__b3bp_tmp_opt:0:1}"
-        debug "cli arg ${__b3bp_tmp_varname} = (${__b3bp_tmp_default}) -> ${!__b3bp_tmp_varname}"
-          # shellcheck disable=SC2004
-        __b3bp_tmp_value=$((${!__b3bp_tmp_varname} + 1))
-        printf -v "${__b3bp_tmp_varname}" '%s' "${__b3bp_tmp_value}"
-      else
-        # repeatable args, they get appended to an array
-        __b3bp_tmp_varname="arg_${__b3bp_tmp_opt:0:1}[@]"
-        debug "cli arg ${__b3bp_tmp_varname} append ${__b3bp_tmp_value}"
-        declare -a "${__b3bp_tmp_varname}"='("${!__b3bp_tmp_varname}" "${__b3bp_tmp_value}")'
-      fi
-    else
-      # non-repeatables
-      __b3bp_tmp_varname="arg_${__b3bp_tmp_opt:0:1}"
-      __b3bp_tmp_default="${!__b3bp_tmp_varname}"
-
-      if [[ -z "${OPTARG}" ]]; then
-        __b3bp_tmp_value=$((__b3bp_tmp_default + 1))
-      fi
-
-      printf -v "${__b3bp_tmp_varname}" '%s' "${__b3bp_tmp_value}"
-
-      debug "cli arg ${__b3bp_tmp_varname} = (${__b3bp_tmp_default}) -> ${!__b3bp_tmp_varname}"
-    fi
-  done
-  set -o nounset # no more unbound variable references expected
-
-  shift $((OPTIND-1))
-
-  if [[ "${1:-}" = "--" ]] ; then
-    shift
-  fi
-fi
-
-
-### Automatic validation of required option arguments
-##############################################################################
-
-for __b3bp_tmp_varname in ${!__b3bp_tmp_has_arg_*}; do
-  # validate only options which required an argument
-  [[ "${!__b3bp_tmp_varname}" = "2" ]] || continue
-
-  __b3bp_tmp_opt_short="${__b3bp_tmp_varname##*_}"
-  __b3bp_tmp_varname="arg_${__b3bp_tmp_opt_short}"
-  [[ "${!__b3bp_tmp_varname}" ]] && continue
-
-  __b3bp_tmp_varname="__b3bp_tmp_opt_short2long_${__b3bp_tmp_opt_short}"
-  printf -v "__b3bp_tmp_opt_long" '%s' "${!__b3bp_tmp_varname}"
-  [[ "${__b3bp_tmp_opt_long:-}" ]] && __b3bp_tmp_opt_long=" (--${__b3bp_tmp_opt_long//_/-})"
-
-  help "Option -${__b3bp_tmp_opt_short}${__b3bp_tmp_opt_long:-} requires an argument"
-done
-
-
-### Cleanup Environment variables
-##############################################################################
-
-for __tmp_varname in ${!__b3bp_tmp_*}; do
-  unset -v "${__tmp_varname}"
-done
-
-unset -v __tmp_varname
-
-
-### Externally supplied __usage. Nothing else to do here
-##############################################################################
-
-if [[ "${__b3bp_external_usage:-}" = "true" ]]; then
-  unset -v __b3bp_external_usage
-  return
-fi
-
-
-### Signal trapping and backtracing
-##############################################################################
-
-function __b3bp_cleanup_before_exit () {
-  info "Cleaning up. Done"
-}
-trap __b3bp_cleanup_before_exit EXIT
-
-# requires `set -o errtrace`
-__b3bp_err_report() {
-    local error_code=${?}
-    error "Error in ${__file} in function ${1} on line ${2}"
-    exit ${error_code}
-}
-# Uncomment the following line for always providing an error backtrace
-# trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
-
-
-### Command-line argument switches (like -d for debugmode, -h for showing helppage)
-##############################################################################
-
-# debug mode
-if [[ "${arg_d:?}" = "1" ]]; then
-  set -o xtrace
-  PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
-  LOG_LEVEL="7"
-  # Enable error backtracing
-  trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
-fi
-
-# verbose mode
-if [[ "${arg_v:?}" = "1" ]]; then
-  set -o verbose
-fi
-
-# no color mode
-if [[ "${arg_n:?}" = "1" ]]; then
-  NO_COLOR="true"
-fi
-
-# help mode
-if [[ "${arg_h:?}" = "1" ]]; then
-  # Help exists with code 1
-  help "Help using ${0}"
-fi
-
-
-### Validation. Error out if the things required for your script are not present
-##############################################################################
-
-[[ "${arg_f:-}" ]]     || help      "Setting a filename with -f or --file is required"
-[[ "${LOG_LEVEL:-}" ]] || emergency "Cannot continue without LOG_LEVEL. "
-
-
-### Runtime
-##############################################################################
-
-info "__i_am_main_script: ${__i_am_main_script}"
-info "__file: ${__file}"
-info "__dir: ${__dir}"
-info "__base: ${__base}"
-info "OSTYPE: ${OSTYPE}"
-
-info "arg_f: ${arg_f}"
-info "arg_d: ${arg_d}"
-info "arg_v: ${arg_v}"
-info "arg_h: ${arg_h}"
-
-# shellcheck disable=SC2015
-if [[ -n "${arg_i:-}" ]] && declare -p arg_i 2> /dev/null | grep -q '^declare \-a'; then
-  info "arg_i:"
-  for input_file in "${arg_i[@]}"; do
-    info " - ${input_file}"
-  done
-elif [[ -n "${arg_i:-}" ]]; then
-  info "arg_i: ${arg_i}"
-else
-  info "arg_i: 0"
-fi
-
-# shellcheck disable=SC2015
-if [[ -n "${arg_x:-}" ]] && declare -p arg_x 2> /dev/null | grep -q '^declare \-a'; then
-  info "arg_x: ${#arg_x[@]}"
-elif [[ -n "${arg_x:-}" ]]; then
-  info "arg_x: ${arg_x}"
-else
-  info "arg_x: 0"
-fi
-
-info "$(echo -e "multiple lines example - line #1\\nmultiple lines example - line #2\\nimagine logging the output of 'ls -al /path/'")"
-
-# All of these go to STDERR, so you can use STDOUT for piping machine readable information to other software
-debug "Info useful to developers for debugging the application, not useful during operations."
-info "Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required."
-notice "Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required."
-warning "Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time."
-error "Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time."
-critical "Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection."
-alert "Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection."
-emergency "A \"panic\" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call."

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/package.json

@@ -1,29 +0,0 @@
-{
-  "name": "bash3boilerplate",
-  "description": "Copypastable templates to write better bash scripts",
-  "version": "2.7.2",
-  "packageManager": "yarn@3.6.0+sha224.19e47520fa56c6146388fdeb438d9dcf6630c3f277a2e1180995c3bb",
-  "engines": {
-    "node": ">= 18",
-    "yarn": "3.6.0"
-  },
-  "scripts": {
-    "lint:shellcheck": "shellcheck --severity=${SHELLCHECK_SEVERITY:-info} $(find . -name '*.sh' -maxdepth 2)",
-    "lint:style": "test/style.pl $(find . -name '*.sh' -maxdepth 2)",
-    "lint": "npm-run-all -l 'lint:**'",
-    "release:major": "env SEMANTIC=major yarn release",
-    "release:minor": "env SEMANTIC=minor yarn release",
-    "release:patch": "env SEMANTIC=patch yarn release",
-    "release": "npm version ${SEMANTIC:-patch} -m \"Release %s\" && yarn version:replace && git commit main.sh src/*.sh -m 'Update version' && git push && git push --tags -f && npm publish",
-    "test:debug:main:repeated": "env LOG_LEVEL=7 test/acceptance.sh main-repeated",
-    "test:update": "env SAVE_FIXTURES=true yarn test",
-    "test": "test/acceptance.sh",
-    "version:current": "node -e 'console.log(require(\"./package.json\").version)'",
-    "version:replace": "replace 'v\\d+\\.\\d+\\.\\d+' \"v$(npm run --silent version:current)\" main.sh src/*.sh"
-  },
-  "devDependencies": {
-    "fakefile": "1.1.0",
-    "npm-run-all": "4.1.5",
-    "replace": "1.2.2"
-  }
-}

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/ini_val.sh

@@ -1,113 +0,0 @@
-#!/usr/bin/env bash
-# BASH3 Boilerplate: ini_val
-#
-# This file:
-#
-#  - Can read and write .ini files using pure bash
-#
-# Limitations:
-#
-#  - All keys inside a section of the .ini file must be unique
-#  - Optional comment parameter for the creation of new entries
-#
-# Usage as a function:
-#
-#  source ini_val.sh
-#  ini_val data.ini connection.host 127.0.0.1 "Host name or IP address"
-#
-# Usage as a command:
-#
-#  ini_val.sh data.ini connection.host 127.0.0.1 "Host name or IP address"
-#
-# Based on a template by BASH3 Boilerplate vv2.7.2
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-function ini_val() {
-  local file="${1:-}"
-  local sectionkey="${2:-}"
-  local val="${3:-}"
-  local comment="${4:-}"
-  local delim="="
-  local comment_delim=";"
-  local section=""
-  local key=""
-  local current=""
-  # add default section
-  local section_default="default"
-
-  if [[ ! -f "${file}" ]]; then
-    # touch file if not exists
-    touch "${file}"
-  fi
-
-  # Split on . for section. However, section is optional
-  IFS='.' read -r section key <<< "${sectionkey}"
-  if [[ ! "${key}" ]]; then
-    key="${section}"
-    # default section if not given
-    section="${section_default}"
-  fi
-
-  # get current value (if exists)
-  current=$(sed -En "/^\[/{h;d;};G;s/^${key}([[:blank:]]*)${delim}(.*)\n\[${section}\]$/\2/p" "${file}"|awk '{$1=$1};1')
-  # get current comment (if exists)
-  current_comment=$(sed -En "/^\[${section}\]/,/^\[.*\]/ s|^(${comment_delim}\[${key}\])(.*)|\2|p" "${file}"|awk '{$1=$1};1')
-
-  if ! grep -q "\[${section}\]" "${file}"; then
-    # create section if not exists (empty line to seperate new section for better readability)
-    echo  >> "${file}"
-    echo "[${section}]" >> "${file}"
-  fi
-
-  if [[ ! "${val}" ]]; then
-    # get a value
-    echo "${current}"
-  else
-    # set a value
-    if [[ ! "${section}" ]]; then
-      # if no section is given, propagate the default section
-      section=${section_default}
-    fi
-
-    if [[ ! "${comment}" ]]; then
-      # if no comment given, keep old comment
-      comment="${current_comment}"
-    fi
-    # maintenance area
-    # a) remove comment if new given / respect section
-    sed -i.bak "/^\[${section}\]/,/^\[.*\]/ s|^\(${comment_delim}\[${key}\] \).*$||" "${file}"
-    # b) remove old key / respect section
-    sed -i.bak "/^\[${section}\]/,/^\[.*\]/ s|^\(${key}=\).*$||" "${file}"
-    # c) remove all empty lines in ini file
-    sed -i.bak '/^[[:space:]]*$/d' "${file}"
-    # d) insert line break before every section for better readability
-    sed -i.bak $'s/^\\[/\\\n\\[/g' "${file}"
-
-    # add to section
-    if [[ ! "${comment}" ]]; then
-      # add new key/value _without_ comment
-      RET="/\\[${section}\\]/a\\
-${key}${delim}${val}"
-    else
-      # add new key/value _with_ preceeding comment
-      RET="/\\[${section}\\]/a\\
-${comment_delim}[${key}] ${comment}\\
-${key}${delim}${val}"
-    fi
-    sed -i.bak -e "${RET}" "${file}"
-    # this .bak dance is done for BSD/GNU portability: http://stackoverflow.com/a/22084103/151666
-    rm -f "${file}.bak"
-  fi
-}
-
-if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
-  export -f ini_val
-else
-  ini_val "${@}"
-  exit ${?}
-fi

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/megamount.sh

@@ -1,78 +0,0 @@
-#!/usr/bin/env bash
-# BASH3 Boilerplate: megamount
-#
-# This file:
-#
-#  - Takes a URL (smb, nfs, afs) and tries to mount it at a given target directory
-#  - Forcefully unmounts any active mount at the target directory first
-#  - Displays the mount's contents for verification
-#
-# Depends on:
-#
-#  - ./parse_url.sh
-#
-# Usage as a function:
-#
-#  source megamount.sh
-#  megamount smb://janedoe:abc123@192.168.0.1/documents /mnt/documents
-#
-# Usage as a command:
-#
-#  megamount.sh smb://janedoe:abc123@192.168.0.1/documents /mnt/documents
-#
-# Based on a template by BASH3 Boilerplate vv2.7.2
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-# shellcheck source=src/parse_url.sh
-source "${__dir}/parse_url.sh"
-
-function megamount () {
-  local url="${1}"
-  local target="${2}"
-
-  local proto
-  local user
-  local pass
-  local host
-  local port
-  local path
-
-  proto=$(parse_url "${url}" "proto")
-  user=$(parse_url "${url}" "user")
-  pass=$(parse_url "${url}" "pass")
-  host=$(parse_url "${url}" "host")
-  port=$(parse_url "${url}" "port")
-  path=$(parse_url "${url}" "path")
-
-  (umount -lf "${target}" || umount -f "${target}") > /dev/null 2>&1 || true
-  mkdir -p "${target}"
-  if [[ "${proto}" = "smb://" ]]; then
-    mount -t cifs --verbose -o "username=${user},password=${pass},hard" "//${host}/${path}" "${target}"
-  elif [[ "${proto}" = "afp://" ]]; then
-    # start syslog-ng
-    # afpfsd || echo "Unable to run afpfsd. Does /dev/log exist?" && exit 1
-    mount_afp "${url}" "${target}"
-  elif [[ "${proto}" = "nfs://" ]]; then
-    mount -t nfs --verbose -o "vers=3,nolock,soft,intr,rsize=32768,wsize=32768" "${host}:/${path}" "${target}"
-  else
-    echo "ERR: Unknown protocol: '${proto}'"
-    exit 1
-  fi
-
-  # chmod 777 "${target}"
-  ls -al "${target}/"
-}
-
-if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
-  export -f megamount
-else
-  megamount "${@}"
-  exit ${?}
-fi

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/parse_url.sh

@@ -1,84 +0,0 @@
-#!/usr/bin/env bash
-# BASH3 Boilerplate: parse_url
-#
-# This file:
-#
-#  - Takes a URL and parses protocol, user, pass, host, port, path.
-#
-# Based on:
-#
-#  - http://stackoverflow.com/a/6174447/151666
-#
-# Usage as a function:
-#
-#  source parse_url.sh
-#  parse_url 'http://johndoe:abc123@example.com:8080/index.html' pass
-#
-# Usage as a command:
-#
-#  parse_url.sh 'http://johndoe:abc123@example.com:8080/index.html'
-#
-# Based on a template by BASH3 Boilerplate vv2.7.2
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-function parse_url() {
-  local parse="${1}"
-  local need="${2:-}"
-
-  local proto
-  local url
-  local userpass
-  local user
-  local pass
-  local hostport
-  local host
-  local port
-  local path
-
-  proto="$(echo "${parse}" | grep :// | sed -e's,^\(.*://\).*,\1,g')"
-  url="${parse/${proto}/}"
-  userpass="$(echo "${url}" | grep @ | cut -d@ -f1)"
-  user="$(echo "${userpass}" | grep : | cut -d: -f1)"
-  pass="$(echo "${userpass}" | grep : | cut -d: -f2)"
-  hostport="$(echo "${url/${userpass}@/}" | cut -d/ -f1)"
-  host="$(echo "${hostport}" | grep : | cut -d: -f1)"
-  port="$(echo "${hostport}" | grep : | cut -d: -f2)"
-  path="$(echo "${url}" | grep / | cut -d/ -f2-)"
-
-  [[ ! "${user}" ]] && user="${userpass}"
-  [[ ! "${host}" ]] && host="${hostport}"
-  if [[ ! "${port}" ]]; then
-    [[ "${proto}" = "http://" ]]  && port="80"
-    [[ "${proto}" = "https://" ]] && port="443"
-    [[ "${proto}" = "mysql://" ]] && port="3306"
-    [[ "${proto}" = "redis://" ]] && port="6379"
-  fi
-
-  if [[ "${need}" ]]; then
-    echo "${!need}"
-  else
-    echo ""
-    echo " Use second argument to return just 1 variable."
-    echo " parse_url() demo: "
-    echo ""
-    echo "   proto: ${proto}"
-    echo "   user:  ${user}"
-    echo "   pass:  ${pass}"
-    echo "   host:  ${host}"
-    echo "   port:  ${port}"
-    echo "   path:  ${path}"
-    echo ""
-  fi
-}
-
-if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
-  export -f parse_url
-else
-  parse_url "${@}"
-  exit ${?}
-fi

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/templater.sh

@@ -1,68 +0,0 @@
-#!/usr/bin/env bash
-# BASH3 Boilerplate: templater
-#
-# This file:
-#
-#  - takes a source (template) & destination (config) filepath argument
-#  - then replaces placeholders with variables found in the environment
-#
-# Usage as a function:
-#
-#  source templater.sh
-#  export NAME=kevin
-#  templater input.cfg output.cfg
-#
-# Usage as a command:
-#
-#  ALLOW_REMAINDERS=1 templater.sh input.cfg output.cfg
-#
-# Based on a template by BASH3 Boilerplate vv2.7.2
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-function templater() {
-  ALLOW_REMAINDERS="${ALLOW_REMAINDERS:-0}"
-
-  templateSrc="${1:-}"
-  templateDst="${2:-}"
-
-  if [[ ! -f "${templateSrc}" ]]; then
-    echo "ERROR: Template source '${templateSrc}' needs to exist"
-    exit 1
-  fi
-  if [[ ! "${templateDst}" ]]; then
-    echo "ERROR: Template destination '${templateDst}' needs to be specified"
-    exit 1
-  fi
-
-  if [[ "$(command -v perl)" ]]; then
-    perl -p -e 's/\$\{(\w+)\}/(exists $ENV{$1} ? $ENV{$1} : "\${$1}")/eg' < "${templateSrc}" > "${templateDst}"
-  else
-    cp -f "${templateSrc}" "${templateDst}"
-
-    for var in $(env |awk -F= '{print $1}' |grep -E '^(_[A-Z0-9_]+|[A-Z0-9][A-Z0-9_]*)$'); do
-      sed -i.bak -e "s#\${${var}}#${!var//#/\\#/}#g" "${templateDst}"
-      # this .bak dance is done for BSD/GNU portability: http://stackoverflow.com/a/22084103/151666
-      rm -f "${templateDst}.bak"
-    done
-  fi
-
-  # cat "${templateDst}"
-
-  # shellcheck disable=SC2016
-  if grep '${' "${templateDst}" && [[ "${ALLOW_REMAINDERS}" = "0" ]]; then
-    echo "ERROR: Unable to replace the above template vars"
-    exit 1
-  fi
-}
-
-if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
-  export -f templater
-else
-  templater "${@}"
-  exit ${?}
-fi

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/acceptance.sh

@@ -1,232 +0,0 @@
-#!/usr/bin/env bash
-# This file:
-#
-#  - Executes one (or all) test scenarios
-#  - Replaces dynamic things like hostnames, IPs, dates, etc
-#  - Optionally saves the results as fixtures, that later runs will be compared against
-#
-# Usage:
-#
-#  ./deploy.sh
-#
-# Based on a template by BASH3 Boilerplate v2.0.0
-# http://bash3boilerplate.sh/#authors
-#
-# The MIT License (MIT)
-# Copyright (c) 2013 Kevin van Zonneveld and contributors
-# You are not obligated to bundle the LICENSE file with your b3bp projects as long
-# as you leave these references intact in the header comments of your source files.
-
-# Exit on error. Append || true if you expect an error.
-set -o errexit
-# Exit on error inside any functions or subshells.
-set -o errtrace
-# Do not allow use of undefined vars. Use ${VAR:-} to use an undefined VAR
-set -o nounset
-# Catch the error in case mysqldump fails (but gzip succeeds) in `mysqldump |gzip`
-set -o pipefail
-# Turn on traces, useful while debugging but commented out by default
-# set -o xtrace
-
-# Set magic variables for current file, directory, os, etc.
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__file="${__dir}/$(basename "${BASH_SOURCE[0]}")"
-__base="$(basename "${__file}" .sh)"
-__root="$(cd "$(dirname "${__dir}")" && pwd)"
-
-__sysTmpDir="${TMPDIR:-/tmp}"
-__sysTmpDir="${__sysTmpDir%/}" # <-- remove trailing slash on macosx
-__accptstTmpDir=$(mktemp -d "${__sysTmpDir}/${__base}.XXXXXX")
-
-function cleanup_before_exit () { rm -r "${__accptstTmpDir:?}"; }
-trap cleanup_before_exit EXIT
-
-cmdSed="sed"
-cmdTimeout="timeout"
-
-if [[ "${OSTYPE}" = "darwin"* ]]; then
-  cmdSed="gsed"
-  cmdTimeout="gtimeout"
-fi
-
-if [[ ! "$(command -v ${cmdSed})" ]]; then
-  echo "Please install ${cmdSed}"
-  exit 1
-fi
-
-if [[ ! "$(command -v ${cmdTimeout})" ]]; then
-  echo "Please install ${cmdTimeout}"
-  exit 1
-fi
-
-__node="$(command -v node)"
-__arch="amd64"
-
-# explicitly setting NO_COLOR to false will make b3bp ignore TERM
-# not being "xterm*" or "screen*" and STDERR not being connected to a terminal
-# it's the opposite of NO_COLOR="true" - it forces color, no matter what
-export NO_COLOR="false"
-
-# Running prepare before other scenarios is important on Travis,
-# so that stdio can diverge - and we can enforce stricter
-# stdio comparison on all other tests.
-while IFS=$'\n' read -r scenario; do
-  scenario="$(dirname "${scenario}")"
-  scenario="${scenario##${__dir}/scenario/}"
-
-  [[ "${scenario}" = "prepare" ]] && continue
-  [[ "${1:-}" ]] && [[ "${scenario}" != "${1}" ]] && continue
-
-  echo "==> Scenario: ${scenario}"
-  pushd "${__dir}/scenario/${scenario}" > /dev/null
-
-    # Run scenario
-    (${cmdTimeout} --kill-after=6m 5m bash ./run.sh \
-      > "${__accptstTmpDir}/${scenario}.stdio" 2>&1; \
-      echo "${?}" > "${__accptstTmpDir}/${scenario}.exitcode" \
-    ) || true
-
-    # Clear out environmental specifics
-    for typ in stdio exitcode; do
-      curFile="${__accptstTmpDir}/${scenario}.${typ}"
-      "${cmdSed}" -i \
-        -e "s@${__node}@{node}@g" "${curFile}" \
-        -e "s@${__root}@{root}@g" "${curFile}" \
-        -e "s@${__sysTmpDir}@{tmpdir}@g" "${curFile}" \
-        -e "s@/tmp@{tmpdir}@g" "${curFile}" \
-        -e "s@${HOME:-/home/travis}@{home}@g" "${curFile}" \
-        -e "s@${USER:-travis}@{user}@g" "${curFile}" \
-        -e "s@travis@{user}@g" "${curFile}" \
-        -e "s@kvz@{user}@g" "${curFile}" \
-        -e "s@{root}/node_modules/\\.bin/node@{node}@g" "${curFile}" \
-        -e "s@{home}/build/{user}/fre{node}@{node}@g" "${curFile}" \
-        -e "s@${HOSTNAME}@{hostname}@g" "${curFile}" \
-        -e "s@${__arch}@{arch}@g" "${curFile}" \
-        -e "s@${OSTYPE}@{OSTYPE}@g" "${curFile}" \
-        -e "s@OSX@{os}@g" "${curFile}" \
-        -e "s@Linux@{os}@g" "${curFile}" \
-      || false
-
-      if grep -q 'ACCPTST:STDIO_REPLACE_IPS' "${curFile}"; then
-        "${cmdSed}" -i \
-          -r 's@[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}@{ip}@g' \
-        "${curFile}"
-
-        # IPs vary in length. Ansible uses padding. {ip} does not vary in length
-        # so kill the padding after it for consistent output
-        "${cmdSed}" -i \
-          -r 's@\{ip\}\s+@{ip} @g' \
-        "${curFile}"
-      fi
-      if grep -q 'ACCPTST:STDIO_REPLACE_UUIDS' "${curFile}"; then
-        "${cmdSed}" -i \
-          -r 's@[0-9a-f\-]{32,40}@{uuid}@g' \
-        "${curFile}"
-      fi
-      if grep -q 'ACCPTST:STDIO_REPLACE_BIGINTS' "${curFile}"; then
-        # Such as: 3811298194
-        "${cmdSed}" -i \
-          -r 's@[0-9]{7,64}@{bigint}@g' \
-        "${curFile}"
-      fi
-      if grep -q 'ACCPTST:STDIO_REPLACE_DATETIMES' "${curFile}"; then
-        # Such as: 2016-02-10 15:38:44.420094
-        "${cmdSed}" -i \
-          -r 's@[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}@{datetime}@g' \
-        "${curFile}"
-      fi
-      if grep -q 'ACCPTST:STDIO_REPLACE_LONGTIMES' "${curFile}"; then
-        # Such as: 2016-02-10 15:38:44.420094
-        "${cmdSed}" -i \
-          -r 's@[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}@{longtime}@g' \
-        "${curFile}"
-      fi
-      if grep -q 'ACCPTST:STDIO_REPLACE_DURATIONS' "${curFile}"; then
-        # Such as: 0:00:00.001991
-        "${cmdSed}" -i \
-          -r 's@[0-9]{1,2}:[0-9]{2}:[0-9]{2}.[0-9]{6}@{duration}@g' \
-        "${curFile}"
-      fi
-      if grep -q 'ACCPTST:STDIO_REPLACE_REMOTE_EXEC' "${curFile}"; then
-        grep -Ev 'remote-exec\): [ a-zA-Z]' "${curFile}" > "${__sysTmpDir}/accptst-filtered.txt"
-        mv "${__sysTmpDir}/accptst-filtered.txt" "${curFile}"
-      fi
-    done
-
-    # Save these as new fixtures?
-    if [[ "${SAVE_FIXTURES:-}" = "true" ]]; then
-      for typ in stdio exitcode; do
-        curFile="${__accptstTmpDir}/${scenario}.${typ}"
-        cp -f \
-          "${curFile}" \
-          "${__dir}/fixture/${scenario}.${typ}"
-      done
-    fi
-
-    # Compare
-    for typ in stdio exitcode; do
-      curFile="${__accptstTmpDir}/${scenario}.${typ}"
-
-      echo -n "    comparing ${typ}.. "
-
-      if [[ "${typ}" = "stdio" ]]; then
-        if grep -q 'ACCPTST:STDIO_SKIP_COMPARE' "${curFile}"; then
-          echo "skip"
-          continue
-        fi
-      fi
-
-      if ! diff --strip-trailing-cr "${__dir}/fixture/${scenario}.${typ}" "${curFile}"; then
-        echo -e "\\n\\n==> MISMATCH OF: ${scenario}.${typ} ---^"
-        echo -e "\\n\\n==> EXPECTED STDIO: "
-        cat "${__dir}/fixture/${scenario}.stdio" || true
-        echo -e "\\n\\n==> ACTUAL STDIO: "
-        cat "${__accptstTmpDir}/${scenario}.stdio" || true
-        exit 1
-      fi
-
-      echo "✓"
-    done
-
-  popd > /dev/null
-done <<< "$(find "${__dir}/scenario" -type f -iname 'run.sh')"
-
-[[ "${1:-}" ]] && exit 0
-
-# Ensure correct syntax with all available bashes
-
-# shellcheck disable=SC2230
-# "command -v" is not a substitute for "which -a"
-while IFS=$'\n' read -r bash; do
-  if [[ "${bash:-}" = "" ]]; then
-    continue
-  fi
-  # shellcheck disable=SC2016
-  echo "==> ${bash} -n $(${bash} -c 'echo "(${BASH_VERSION})"')"
-  pushd "${__root}" > /dev/null
-
-  failed="false"
-
-  while IFS=$'\n' read -r file; do
-    [[ "${file}" =~ ^\./node_modules/ ]] && continue
-
-    echo -n "    ${file}.. "
-
-    if ! "${bash}" -n "${file}" 2>> "${__accptstTmpDir}/${bash//\//.}.err"; then
-      echo "✗"
-      failed="true"
-      continue
-    fi
-
-    echo "✓"
-  done <<< "$(find . -type f -iname '*.sh')"
-
-  popd > /dev/null
-
-  if [[ "${failed}" = "true" ]]; then
-    cat "${__accptstTmpDir}/${bash//\//.}.err"
-    exit 1
-  fi
-done <<< "$(which -a bash 2>/dev/null)"
-
-exit 0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/double-source.exitcode

@@ -1 +0,0 @@
-1

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/double-source.stdio

@@ -1,25 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-{datetime} UTC [    debug] cli arg arg_f = () -> {tmpdir}/x
-{datetime} UTC [     info] __i_am_main_script: 0
-{datetime} UTC [     info] __file: {root}/example.sh
-{datetime} UTC [     info] __dir: {root}
-{datetime} UTC [     info] __base: example
-{datetime} UTC [     info] OSTYPE: {OSTYPE}
-{datetime} UTC [     info] arg_f: {tmpdir}/x
-{datetime} UTC [     info] arg_d: 0
-{datetime} UTC [     info] arg_v: 0
-{datetime} UTC [     info] arg_h: 0
-{datetime} UTC [     info] arg_i: 0
-{datetime} UTC [     info] arg_x: 0
-{datetime} UTC [     info] multiple lines example - line #1
-{datetime} UTC [     info] multiple lines example - line #2
-{datetime} UTC [     info] imagine logging the output of 'ls -al /path/'
-{datetime} UTC [    debug] Info useful to developers for debugging the application, not useful during operations.
-{datetime} UTC [     info] Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
-{datetime} UTC [   notice] Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
-{datetime} UTC [  warning] Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
-{datetime} UTC [    error] Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
-{datetime} UTC [ critical] Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
-{datetime} UTC [    alert] Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
-{datetime} UTC [emergency] A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
-{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/ini_val.exitcode

@@ -1 +0,0 @@
-0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/ini_val.stdio

@@ -1,42 +0,0 @@
---> command: Read 3 values
-exists
-127.0.0.1
-nginx, nodejs
-
---> command: Replace three values in-place and show result
-
-[default]
-orphan=no more
-
-[connection]
-host=192.168.0.1
-
-[software]
-packages=vim
-
-[comment]
-;[command] got this new comment
-command=works like a chame
-;[new_command] last addition will be moved downwards again after next command
-new_command=commented too
---> function: Read 3 values
-exists
-127.0.0.1
-nginx, nodejs
-
---> function: Replace three values in-place and show result
-
-[default]
-orphan=no more
-
-[connection]
-host=192.168.0.1
-
-[software]
-packages=vim
-
-[comment]
-;[command] got this new comment
-command=works like a chame
-;[new_command] last addition will be moved downwards again after next command
-new_command=commented too

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-debug.exitcode

@@ -1 +0,0 @@
-1

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-debug.stdio

@@ -1,25 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-{datetime} UTC [    debug] cli arg arg_f = () -> {tmpdir}/x
-{datetime} UTC [     info] __i_am_main_script: 1
-{datetime} UTC [     info] __file: {root}/main.sh
-{datetime} UTC [     info] __dir: {root}
-{datetime} UTC [     info] __base: main
-{datetime} UTC [     info] OSTYPE: {OSTYPE}
-{datetime} UTC [     info] arg_f: {tmpdir}/x
-{datetime} UTC [     info] arg_d: 0
-{datetime} UTC [     info] arg_v: 0
-{datetime} UTC [     info] arg_h: 0
-{datetime} UTC [     info] arg_i: 0
-{datetime} UTC [     info] arg_x: 0
-{datetime} UTC [     info] multiple lines example - line #1
-{datetime} UTC [     info] multiple lines example - line #2
-{datetime} UTC [     info] imagine logging the output of 'ls -al /path/'
-{datetime} UTC [    debug] Info useful to developers for debugging the application, not useful during operations.
-{datetime} UTC [     info] Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
-{datetime} UTC [   notice] Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
-{datetime} UTC [  warning] Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
-{datetime} UTC [    error] Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
-{datetime} UTC [ critical] Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
-{datetime} UTC [    alert] Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
-{datetime} UTC [emergency] A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
-{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-help.exitcode

@@ -1 +0,0 @@
-1

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-help.stdio

@@ -1,19 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-
- Help using {root}/main.sh
-
-  -f --file  [arg] Filename to process. Required.
-  -t --temp  [arg] Location of tempfile. Default="{tmpdir}/bar"
-  -v               Enable verbose mode, print script as it is executed
-  -d --debug       Enables debug mode
-  -h --help        This page
-  -n --no-color    Disable color output
-  -1 --one         Do just one thing
-  -i --input [arg] File to process. Can be repeated.
-  -x               Specify a flag. Can be repeated.
-
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-
-{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-longopt.exitcode

@@ -1 +0,0 @@
-0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-longopt.stdio

@@ -1,4 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-{datetime} UTC [     info] arg_f: {tmpdir}/x
-{datetime} UTC [     info] arg_f: {tmpdir}/x
-{datetime} UTC [     info] arg_f: {tmpdir}/x

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-nocolor.exitcode

@@ -1 +0,0 @@
-1

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-nocolor.stdio

@@ -1,25 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-{datetime} UTC [    debug] cli arg arg_f = () -> {tmpdir}/x
-{datetime} UTC [     info] __i_am_main_script: 1
-{datetime} UTC [     info] __file: {root}/main.sh
-{datetime} UTC [     info] __dir: {root}
-{datetime} UTC [     info] __base: main
-{datetime} UTC [     info] OSTYPE: {OSTYPE}
-{datetime} UTC [     info] arg_f: {tmpdir}/x
-{datetime} UTC [     info] arg_d: 0
-{datetime} UTC [     info] arg_v: 0
-{datetime} UTC [     info] arg_h: 0
-{datetime} UTC [     info] arg_i: 0
-{datetime} UTC [     info] arg_x: 0
-{datetime} UTC [     info] multiple lines example - line #1
-{datetime} UTC [     info] multiple lines example - line #2
-{datetime} UTC [     info] imagine logging the output of 'ls -al /path/'
-{datetime} UTC [    debug] Info useful to developers for debugging the application, not useful during operations.
-{datetime} UTC [     info] Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
-{datetime} UTC [   notice] Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
-{datetime} UTC [  warning] Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
-{datetime} UTC [    error] Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
-{datetime} UTC [ critical] Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
-{datetime} UTC [    alert] Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
-{datetime} UTC [emergency] A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
-{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-repeated.exitcode

@@ -1 +0,0 @@
-0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-repeated.stdio

@@ -1,9 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-{datetime} UTC [     info] arg_i:
-{datetime} UTC [     info]  - simple_input
-{datetime} UTC [     info]  - input_in_quotes
-{datetime} UTC [     info]  - input with spaces
-{datetime} UTC [     info]  - input with "quotes"
-{datetime} UTC [     info]  - last_input
-{datetime} UTC [     info] arg_x: 3
-{datetime} UTC [     info] arg_x: 4

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-defaults.exitcode

@@ -1 +0,0 @@
-0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-defaults.stdio

@@ -1,7 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-{datetime} UTC [     info] arg_1: 0
-{datetime} UTC [     info] arg_2: 0
-{datetime} UTC [     info] arg_3: 'THREE'
-{datetime} UTC [     info] arg_4: "FOUR"
-{datetime} UTC [     info] arg_5: OOOPS
-{datetime} UTC [     info] arg_6: 

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-validation.exitcode

@@ -1 +0,0 @@
-0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-validation.stdio

@@ -1,169 +0,0 @@
-ACCPTST:STDIO_REPLACE_DATETIMES
-# complain about -3
-
- Option -3 (--three) requires an argument
-
-  -0 --zero        Do nothing.
-  -1 --one         Do one thing. Required.
-                   More description.
-  -2 --two         Do two things.
-                   More. Required. Description.
-  -3 --three [arg] Do three things.
-                   Required.
-  -4 --four  {arg} Do four things.
-  -5 --five  {arg} Do five things. Required. Maybe.
-  -6 --six   [arg] Do six things. Not Required.
-                   Required, it is not.
-  -7 --seven [arg] Required. Or bust.
-  -8 --eight [arg] Do eight things.
-                   More.Required.Description.
-  -a         [arg] Do A.   Required.
-                   Default="do-a"
-  -b         {arg} Do B.Default="do-b"
-  -c         [arg] Required.   Default="do-c"
-  -d         {arg} Default="do-d"
-
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-
-# complain about -4
-
- Option -4 (--four) requires an argument
-
-  -0 --zero        Do nothing.
-  -1 --one         Do one thing. Required.
-                   More description.
-  -2 --two         Do two things.
-                   More. Required. Description.
-  -3 --three [arg] Do three things.
-                   Required.
-  -4 --four  {arg} Do four things.
-  -5 --five  {arg} Do five things. Required. Maybe.
-  -6 --six   [arg] Do six things. Not Required.
-                   Required, it is not.
-  -7 --seven [arg] Required. Or bust.
-  -8 --eight [arg] Do eight things.
-                   More.Required.Description.
-  -a         [arg] Do A.   Required.
-                   Default="do-a"
-  -b         {arg} Do B.Default="do-b"
-  -c         [arg] Required.   Default="do-c"
-  -d         {arg} Default="do-d"
-
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-
-# complain about -5
-
- Option -5 (--five) requires an argument
-
-  -0 --zero        Do nothing.
-  -1 --one         Do one thing. Required.
-                   More description.
-  -2 --two         Do two things.
-                   More. Required. Description.
-  -3 --three [arg] Do three things.
-                   Required.
-  -4 --four  {arg} Do four things.
-  -5 --five  {arg} Do five things. Required. Maybe.
-  -6 --six   [arg] Do six things. Not Required.
-                   Required, it is not.
-  -7 --seven [arg] Required. Or bust.
-  -8 --eight [arg] Do eight things.
-                   More.Required.Description.
-  -a         [arg] Do A.   Required.
-                   Default="do-a"
-  -b         {arg} Do B.Default="do-b"
-  -c         [arg] Required.   Default="do-c"
-  -d         {arg} Default="do-d"
-
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-
-# complain about -8 (because -7 syntax is not supported)
-
- Option -8 (--eight) requires an argument
-
-  -0 --zero        Do nothing.
-  -1 --one         Do one thing. Required.
-                   More description.
-  -2 --two         Do two things.
-                   More. Required. Description.
-  -3 --three [arg] Do three things.
-                   Required.
-  -4 --four  {arg} Do four things.
-  -5 --five  {arg} Do five things. Required. Maybe.
-  -6 --six   [arg] Do six things. Not Required.
-                   Required, it is not.
-  -7 --seven [arg] Required. Or bust.
-  -8 --eight [arg] Do eight things.
-                   More.Required.Description.
-  -a         [arg] Do A.   Required.
-                   Default="do-a"
-  -b         {arg} Do B.Default="do-b"
-  -c         [arg] Required.   Default="do-c"
-  -d         {arg} Default="do-d"
-
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-
-# complain about -d (because -d syntax is not supported)
-
- Option -d requires an argument
-
-  -0 --zero        Do nothing.
-  -1 --one         Do one thing. Required.
-                   More description.
-  -2 --two         Do two things.
-                   More. Required. Description.
-  -3 --three [arg] Do three things.
-                   Required.
-  -4 --four  {arg} Do four things.
-  -5 --five  {arg} Do five things. Required. Maybe.
-  -6 --six   [arg] Do six things. Not Required.
-                   Required, it is not.
-  -7 --seven [arg] Required. Or bust.
-  -8 --eight [arg] Do eight things.
-                   More.Required.Description.
-  -a         [arg] Do A.   Required.
-                   Default="do-a"
-  -b         {arg} Do B.Default="do-b"
-  -c         [arg] Required.   Default="do-c"
-  -d         {arg} Default="do-d"
-
- This is Bash3 Boilerplate's help text. Feel free to add any description of your
- program or elaborate more on command-line arguments. This section is not
- parsed and will be added as-is to the help.
-
-# complain about nothing
-{datetime} UTC [     info] arg_0: 0
-{datetime} UTC [     info] arg_1: 0
-{datetime} UTC [     info] arg_2: 0
-{datetime} UTC [     info] arg_3: arg3
-{datetime} UTC [     info] arg_4: arg4
-{datetime} UTC [     info] arg_5: arg5
-{datetime} UTC [     info] arg_6: 
-{datetime} UTC [     info] arg_7: 
-{datetime} UTC [     info] arg_8: arg8
-{datetime} UTC [     info] arg_a: do-a
-{datetime} UTC [     info] arg_b: do-b
-{datetime} UTC [     info] arg_c: do-c
-{datetime} UTC [     info] arg_d: argd
-# test for issue #108
-{datetime} UTC [     info] arg_0: 1
-{datetime} UTC [     info] arg_1: 0
-{datetime} UTC [     info] arg_2: 0
-{datetime} UTC [     info] arg_3: arg3
-{datetime} UTC [     info] arg_4: value
-{datetime} UTC [     info] arg_5: arg5
-{datetime} UTC [     info] arg_6: 
-{datetime} UTC [     info] arg_7: 
-{datetime} UTC [     info] arg_8: arg8
-{datetime} UTC [     info] arg_a: do-a
-{datetime} UTC [     info] arg_b: do-b
-{datetime} UTC [     info] arg_c: do-c
-{datetime} UTC [     info] arg_d: argd

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/megamount.exitcode

@@ -1 +0,0 @@
-1

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/megamount.stdio

@@ -1,2 +0,0 @@
-ERR: Unknown protocol: 'foobarfs://'
-ERR: Unknown protocol: 'foobarfs://'

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/parse_url.exitcode

@@ -1 +0,0 @@
-0

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/parse_url.stdio

@@ -1,24 +0,0 @@
-abc123
-
- Use second argument to return just 1 variable.
- parse_url() demo: 
-
-   proto: http://
-   user:  johndoe
-   pass:  abc123
-   host:  example.com
-   port:  8080
-   path:  index.html
-
-abc123
-
- Use second argument to return just 1 variable.
- parse_url() demo: 
-
-   proto: http://
-   user:  johndoe
-   pass:  abc123
-   host:  example.com
-   port:  8080
-   path:  index.html
-

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/templater.exitcode

@@ -1 +0,0 @@
-1

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/templater.stdio

@@ -1,14 +0,0 @@
---
-[connection]
-host = 127.0.0.1
---
-[connection]
-host = 127.0.0.1
---
-port = ${I_DONT_EXIST}
-[connection]
-host = 127.0.0.1
-port = ${I_DONT_EXIST}
---
-port = ${I_DONT_EXIST}
-ERROR: Unable to replace the above template vars

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/double-source/run.sh

@@ -1,15 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-export LOG_LEVEL=7
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-# shellcheck source=example.sh
-source "${__root}/example.sh" -f /tmp/x

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/ini_val/data.ini

@@ -1,8 +0,0 @@
-[default]
-orphan=exists
-
-[connection]
-host=127.0.0.1
-
-[software]
-packages=nginx, nodejs

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/ini_val/run.sh

@@ -1,54 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-# Set magic variables for current FILE & DIR
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-# echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-
-# Use as standalone:
-cp -f data.ini dummy.ini
-echo "--> command: Read 3 values"
-bash "${__root}/src/ini_val.sh" ./dummy.ini orphan
-bash "${__root}/src/ini_val.sh" ./dummy.ini connection.host
-bash "${__root}/src/ini_val.sh" ./dummy.ini software.packages
-bash "${__root}/src/ini_val.sh" ./dummy.ini comment.command
-
-echo "--> command: Replace three values in-place and show result"
-bash "${__root}/src/ini_val.sh" ./dummy.ini orphan "no more"
-bash "${__root}/src/ini_val.sh" ./dummy.ini connection.host "192.168.0.1"
-bash "${__root}/src/ini_val.sh" ./dummy.ini software.packages "vim"
-
-bash "${__root}/src/ini_val.sh" ./dummy.ini comment.command "commented" "this key is commented"
-bash "${__root}/src/ini_val.sh" ./dummy.ini comment.new_command "commented too" "last addition will be moved downwards again after next command"
-bash "${__root}/src/ini_val.sh" ./dummy.ini comment.command "works like a chame" "got this new comment"
-cat dummy.ini
-rm -f dummy.ini
-
-# Use as include:
-cp -f data.ini dummy.ini
-
-# shellcheck source=main.sh
-source "${__root}/src/ini_val.sh"
-
-echo "--> function: Read 3 values"
-ini_val ./dummy.ini orphan
-ini_val ./dummy.ini connection.host
-ini_val ./dummy.ini software.packages
-ini_val ./dummy.ini comment.command
-
-echo "--> function: Replace three values in-place and show result"
-ini_val ./dummy.ini orphan "no more"
-ini_val ./dummy.ini connection.host "192.168.0.1"
-ini_val ./dummy.ini software.packages "vim"
-
-ini_val ./dummy.ini comment.command "commented" "this key is commited"
-ini_val ./dummy.ini comment.new_command "commented too" "last addition will be moved downwards again after next command"
-ini_val ./dummy.ini comment.command "works like a chame" "got this new comment"
-cat dummy.ini
-rm -f dummy.ini

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-debug/run.sh

@@ -1,12 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-env LOG_LEVEL=7 bash "${__root}/main.sh" -f /tmp/x

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-help/run.sh

@@ -1,12 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-bash "${__root}/main.sh" -f /tmp/x -h

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-longopt/run.sh

@@ -1,16 +0,0 @@
-#!/usr/bin/env bash
-# set -o pipefail
-# set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-(
-  env LOG_LEVEL=6 bash "${__root}/main.sh" --file /tmp/x;
-  env LOG_LEVEL=6 bash "${__root}/main.sh" --file=/tmp/x;
-  env LOG_LEVEL=6 bash "${__root}/main.sh" -f /tmp/x
-) 2>&1 |grep arg_f

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-nocolor/run.sh

@@ -1,12 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-env LOG_LEVEL=7 NO_COLOR=true bash "${__root}/main.sh" -f /tmp/x

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-repeated/run.sh

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-# set -o pipefail
-# set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-(
-  env LOG_LEVEL="${LOG_LEVEL:-6}" bash "${__root}/main.sh" -f dummy -i simple_input -i "input_in_quotes" -i "input with spaces" -i "input with \"quotes\"" -i last_input
-) 2>&1 |grep arg_i -A 5
-
-(
-  env LOG_LEVEL="${LOG_LEVEL:-6}" bash "${__root}/main.sh" -x -f dummy -x -x
-  env LOG_LEVEL="${LOG_LEVEL:-6}" bash "${__root}/main.sh" -f dummy -xxxx
-) 2>&1 |grep arg_x

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-usage-defaults/run.sh

@@ -1,32 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-read -r -d '' __usage <<-'EOF' || true # exits non-zero when EOF encountered
-  -1 --one         Do one thing. Default="ONE"
-                   More description.
-  -2 --two         Do two things.
-                   More description. Default="TWO"
-  -3 --three [arg] Do three things. Default="'THREE'"
-                   More description.
-  -4 --four  [arg] Do four things.
-                   More description. Default='"FOUR"'
-  -5 --five  [arg] Do five things. Default="FIVE"
-                   More description. Default='OOOPS'
-  -6 --six   [arg] Do six things.
-                   More description.
-EOF
-
-export __usage
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-# shellcheck source=main.sh
-source "${__root}/main.sh"
-
-for argument in ${!arg_*}; do info "${argument}: ${!argument}"; done

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-usage-validation/run.sh

@@ -1,64 +0,0 @@
-#!/usr/bin/env bash
-# shellcheck source=main.sh
-
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-read -r -d '' __usage <<-'EOF' || true # exits non-zero when EOF encountered
-  -0 --zero        Do nothing.
-  -1 --one         Do one thing. Required.
-                   More description.
-  -2 --two         Do two things.
-                   More. Required. Description.
-  -3 --three [arg] Do three things.
-                   Required.
-  -4 --four  {arg} Do four things.
-  -5 --five  {arg} Do five things. Required. Maybe.
-  -6 --six   [arg] Do six things. Not Required.
-                   Required, it is not.
-  -7 --seven [arg] Required. Or bust.
-  -8 --eight [arg] Do eight things.
-                   More.Required.Description.
-  -a         [arg] Do A.   Required.
-                   Default="do-a"
-  -b         {arg} Do B.Default="do-b"
-  -c         [arg] Required.   Default="do-c"
-  -d         {arg} Default="do-d"
-EOF
-
-export __usage
-export NO_COLOR="true"
-
-echo "ACCPTST:STDIO_REPLACE_DATETIMES"
-
-echo "# complain about -3"
-(source "${__root}/main.sh") || true
-
-echo "# complain about -4"
-(source "${__root}/main.sh" -3 arg3) || true
-
-echo "# complain about -5"
-(source "${__root}/main.sh" -3 arg3 -4 arg4) || true
-
-echo "# complain about -8 (because -7 syntax is not supported)"
-(source "${__root}/main.sh" -3 arg3 -4 arg4 -5 arg5) || true
-
-echo "# complain about -d (because -d syntax is not supported)"
-(source "${__root}/main.sh" -3 arg3 -4 arg4 -5 arg5 -8 arg8) || true
-
-echo "# complain about nothing"
-(
-  source "${__root}/main.sh" -3 arg3 -4 arg4 -5 arg5 -8 arg8 -d argd
-  for argument in ${!arg_*}; do info "${argument}: ${!argument}"; done
-)
-
-echo "# test for issue #108"
-(
-  source "${__root}/main.sh" -3 arg3 -5 arg5 -8 arg8 -d argd --four value --zero
-  for argument in ${!arg_*}; do info "${argument}: ${!argument}"; done
-)

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/megamount/run.sh

@@ -1,21 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-__sysTmpDir="${TMPDIR:-/tmp}"
-__sysTmpDir="${__sysTmpDir%/}" # <-- remove trailing slash on macosx
-
-# Currently I only know how to test a failing condition here since
-# it's too invasive to create actual mounts to play with on a system
-
-bash "${__root}/src/megamount.sh" 'foobarfs://janedoe:abc123@192.168.0.1/documents' "${__sysTmpDir}/mnt/documents" || true
-
-# shellcheck source=src/megamount.sh
-source "${__root}/src/megamount.sh"
-
-megamount 'foobarfs://janedoe:abc123@192.168.0.1/documents' "${__sysTmpDir}/mnt/documents"

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/parse_url/run.sh

@@ -1,17 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-bash "${__root}/src/parse_url.sh" 'http://johndoe:abc123@example.com:8080/index.html' pass
-bash "${__root}/src/parse_url.sh" 'http://johndoe:abc123@example.com:8080/index.html'
-
-# shellcheck source=src/parse_url.sh
-source "${__root}/src/parse_url.sh"
-
-parse_url 'http://johndoe:abc123@example.com:8080/index.html' pass
-parse_url 'http://johndoe:abc123@example.com:8080/index.html'

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/templater/app.template.cfg

@@ -1,2 +0,0 @@
-[connection]
-host = ${TARGET_HOST}

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/templater/break.template.cfg

@@ -1,3 +0,0 @@
-[connection]
-host = ${TARGET_HOST}
-port = ${I_DONT_EXIST}

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/templater/run.sh

@@ -1,36 +0,0 @@
-#!/usr/bin/env bash
-set -o pipefail
-set -o errexit
-set -o nounset
-# set -o xtrace
-
-__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-__file="${__dir}/$(basename "${BASH_SOURCE[0]}")"
-__base="$(basename "${__file}" .sh)"
-
-__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
-
-__templaterTmpFile=$(mktemp "${TMPDIR:-/tmp}/${__base}.XXXXXX")
-function cleanup_before_exit () { rm "${__templaterTmpFile:?}"; }
-trap cleanup_before_exit EXIT
-
-echo "--"
-env TARGET_HOST="127.0.0.1" bash "${__root}/src/templater.sh" ./app.template.cfg "${__templaterTmpFile}"
-cat "${__templaterTmpFile}"
-
-echo "--"
-export TARGET_HOST="127.0.0.1"
-
-# shellcheck source=src/templater.sh
-source "${__root}/src/templater.sh"
-
-templater ./app.template.cfg "${__templaterTmpFile}"
-cat "${__templaterTmpFile}"
-
-echo "--"
-env ALLOW_REMAINDERS="1" TARGET_HOST="127.0.0.1" bash "${__root}/src/templater.sh" ./break.template.cfg "${__templaterTmpFile}"
-cat "${__templaterTmpFile}"
-
-echo "--"
-env TARGET_HOST="127.0.0.1" bash "${__root}/src/templater.sh" ./break.template.cfg "${__templaterTmpFile}"
-cat "${__templaterTmpFile}"

vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/style.pl

@@ -1,45 +0,0 @@
-#!/usr/bin/env perl
-
-use strict;
-use warnings;
-
-die "usage: $0 <file>\n" if (not @ARGV);
-
-my $rc = 0;
-my $file = shift;
-
-open(my $fh, '<', $file) or die "Cannot open \`$file' for read: $!\n";
-while (<$fh>) {
-  next if (/^\s*#/);
-
-  my $errors = 0;
-
-  # remove everything between single quotes
-  # this will remove too much in case of: echo "var='$var'"
-  # and thus miss an opportunity to complain later on
-  # also it mangles the input line irreversible
-  s/'[^']+'/'___'/g;
-
-  # highlight unbraced variables--
-  # unless properly backslash'ed
-  $errors += s/((?:^|[^\\]))(((\\\\)+)?\$\w)/$1\033[31m$2\033[0m/g;
-
-  # highlight single square brackets
-  $errors += s/((?:^|\s+))\[([^\[].+[^\]])\](\s*(;|&&|\|\|))/$1\033[31m\[\033[0m$2\033[31m\]\033[0m$3/g;
-
-  # highlight double equal sign
-  $errors += s/(\[\[.*)(==)(.*\]\])/$1\033[31m$2\033[0m$3/g;
-
-  # highlight tabs mixed with whitespace at beginning of lines
-  $errors += s/^( *)(\t+ *)/\033[31m\[$2\]\033[0m/;
-
-  # highlight trailing whitespace
-  $errors += s/([ \t]+)$/\033[31m\[$1\]\033[0m/;
-
-  next if (not $errors);
-  print "${file}[$.]: $_";
-  $rc = 1;
-}
-close($fh);
-
-exit $rc;

vendor/git.knownelement.com/ExternalVendorCode/mo/.eslintrc.yaml

@@ -0,0 +1,168 @@
+parserOptions:
+    ecmaVersion: latest
+    sourceType: module
+env:
+    es6: true
+    jasmine: true
+    node: true
+extends: eslint:recommended
+rules:
+    accessor-pairs: error
+    array-bracket-spacing:
+        - error
+        - never
+    array-callback-return: error
+    block-spacing:
+        - error
+        - never
+    brace-style: error
+    comma-dangle: error
+    comma-spacing: error
+    comma-style: error
+    complexity:
+        - error
+        - 10
+    computed-property-spacing: error
+    consistent-return: error
+    consistent-this: error
+    constructor-super: error
+    curly: error
+    default-case: error
+    dot-notation: error
+    eol-last: error
+    eqeqeq: error
+    generator-star-spacing: error
+    global-require: off
+    guard-for-in: error
+    jsx-quotes: error
+    key-spacing: error
+    keyword-spacing: error
+    linebreak-style: error
+    lines-around-comment:
+        - error
+        -
+            allowBlockStart: true
+            allowObjectStart: true
+            allowArrayStart: true
+    max-statements-per-line: error
+    new-cap: error
+    new-parens: error
+    no-array-constructor: error
+    no-bitwise: error
+    no-caller: error
+    no-case-declarations: error
+    no-catch-shadow: error
+    no-class-assign: error
+    no-cond-assign: error
+    no-confusing-arrow: error
+    no-console: off
+    no-const-assign: error
+    no-constant-condition: error
+    no-continue: error
+    no-delete-var: error
+    no-dupe-args: error
+    no-dupe-class-members: error
+    no-dupe-keys: error
+    no-duplicate-case: error
+    no-duplicate-imports: error
+    no-empty: off
+    no-empty-character-class: error
+    no-empty-pattern: error
+    no-eq-null: error
+    no-eval: error
+    no-extend-native: error
+    no-extra-bind: error
+    no-extra-boolean-cast: error
+    no-extra-label: error
+    no-extra-semi: error
+    no-fallthrough: error
+    no-func-assign: error
+    no-implied-eval: error
+    no-inner-declarations: error
+    no-invalid-this: error
+    no-invalid-regexp: error
+    no-irregular-whitespace: error
+    no-iterator: error
+    no-label-var: error
+    no-labels: error
+    no-lone-blocks: error
+    no-lonely-if: error
+    no-loop-func: error
+    no-mixed-spaces-and-tabs: error
+    no-multi-spaces: error
+    no-multi-str: error
+    no-multiple-empty-lines:
+        - error
+        -
+            max: 2
+    no-native-reassign: error
+    no-negated-condition: error
+    no-nested-ternary: error
+    no-new: error
+    no-new-func: error
+    no-new-object: error
+    no-new-symbol: error
+    no-new-wrappers: error
+    no-obj-calls: error
+    no-octal: error
+    no-octal-escape: error
+    no-path-concat: error
+    no-plusplus: error
+    no-proto: error
+    no-redeclare: error
+    no-regex-spaces: error
+    no-restricted-globals: error
+    no-return-assign: error
+    no-script-url: error
+    no-self-assign: error
+    no-self-compare: error
+    no-sequences: error
+    no-shadow: error
+    no-shadow-restricted-names: error
+    no-spaced-func: error
+    no-sparse-arrays: error
+    no-this-before-super: error
+    no-throw-literal: error
+    no-trailing-spaces: error
+    no-undef: error
+    no-undef-init: error
+    no-unexpected-multiline: error
+    no-unmodified-loop-condition: error
+    no-unneeded-ternary: error
+    no-unreachable: error
+    no-unsafe-finally: error
+    no-unused-expressions: error
+    no-unused-labels: error
+    no-unused-vars: error
+    no-useless-call: error
+    no-useless-computed-key: error
+    no-useless-concat: error
+    no-useless-constructor: error
+    no-useless-escape: error
+    no-void: error
+    no-warning-comments: warn
+    no-whitespace-before-property: error
+    no-with: error
+    operator-assignment: error
+    padded-blocks:
+        - error
+        - never
+    prefer-const: error
+    quote-props:
+        - error
+        - as-needed
+    radix: error
+    require-yield: error
+    semi: error
+    semi-spacing: error
+    space-before-blocks: error
+    space-in-parens: error
+    space-infix-ops:
+        - error
+        -
+            int32Hint: false
+    space-unary-ops: error
+    spaced-comment: error
+    use-isnan: error
+    valid-typeof: error
+    yield-star-spacing: error

vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/ci.yaml

@@ -0,0 +1,13 @@
+name: CI
+on: [push]
+jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v1
+      - name: Run tests
+        run: ./run-tests
+      - name: Run against spec
+        run: ./run-spec

vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/release.yaml

@@ -0,0 +1,45 @@
+name: docker push
+on: [push]
+jobs:
+  push_to_registry:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@master
+      - name: Docker meta
+        if: startsWith(github.ref, 'refs/tags/')
+        id: docker_meta
+        uses: crazy-max/ghaction-docker-meta@v1
+        with:
+          images: ghcr.io/${{ github.repository }}
+          tag-match: v(.*)
+      - name: Set up QEMU
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: docker/setup-qemu-action@v1
+      - name: Set up Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v1
+      - name: Cache Docker layers
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: actions/cache@v2
+        with:
+          path: /tmp/.buildx-cache
+          key: ${{ runner.os }}-buildx-${{ github.sha }}
+          restore-keys: |
+            ${{ runner.os }}-buildx-
+      - name: Login to GitHub Container Registry
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: docker/login-action@v1
+        with:
+          registry: ghcr.io
+          username: ${{ github.repository_owner }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - name:  Build and push
+        uses: docker/build-push-action@v2
+        if: startsWith(github.ref, 'refs/tags/')
+        with:
+          builder: ${{ steps.buildx.outputs.name }}
+          platforms: linux/amd64,linux/arm64
+          tags: ${{ steps.docker_meta.outputs.tags }}
+          cache-from: type=local,src=/tmp/.buildx-cache
+          cache-to: type=local,dest=/tmp/.buildx-cache
+          push: true

vendor/git.knownelement.com/ExternalVendorCode/mo/.gitignore

@@ -0,0 +1,9 @@
+*.swp
+diagnostic.partial
+diagnostic.test
+tests/*.diff
+spec/
+spec-runner/
+node_modules/
+package.json
+package-lock.json

vendor/git.knownelement.com/ExternalVendorCode/mo/API.md

@@ -0,0 +1,616 @@
+API / Function Documentation
+============================
+
+This documentation is generated automatically from the source of [mo] thanks to [tomdoc.sh].
+
+
+`mo()`
+------
+
+Public: Template parser function.  Writes templates to stdout.
+
+* $0 - Name of the mo file, used for getting the help message.
+* $@ - Filenames to parse.
+
+Returns nothing.
+
+
+`mo::debug()`
+-------------
+
+Internal: Show a debug message
+
+* $1 - The debug message to show
+
+Returns nothing.
+
+
+`mo::debugShowState()`
+----------------------
+
+Internal: Show a debug message and internal state information
+
+No arguments
+
+Returns nothing.
+
+
+`mo::error()`
+-------------
+
+Internal: Show an error message and exit
+
+* $1 - The error message to show
+* $2 - Error code
+
+Returns nothing. Exits the program.
+
+
+`mo::errorNear()`
+-----------------
+
+Internal: Show an error message with a snippet of context and exit
+
+* $1 - The error message to show
+* $2 - The starting point
+* $3 - Error code
+
+Returns nothing. Exits the program.
+
+
+`mo::usage()`
+-------------
+
+Internal: Displays the usage for mo.  Pulls this from the file that contained the `mo` function.  Can only work when the right filename comes is the one argument, and that only happens when `mo` is called with `$0` set to this file.
+
+* $1 - Filename that has the help message
+
+Returns nothing.
+
+
+`mo::content()`
+---------------
+
+Internal: Fetches the content to parse into MO_UNPARSED.  Can be a list of partials for files or the content from stdin.
+
+* $1 - Destination variable name
+* $2-@ - File names (optional), read from stdin otherwise
+
+Returns nothing.
+
+
+`mo::contentFile()`
+-------------------
+
+Internal: Read a file into MO_UNPARSED.
+
+* $1 - Destination variable name.
+* $2 - Filename to load - if empty, defaults to /dev/stdin
+
+Returns nothing.
+
+
+`mo::indirect()`
+----------------
+
+Internal: Send a variable up to the parent of the caller of this function.
+
+* $1 - Variable name
+* $2 - Value
+
+Examples
+
+    callFunc () {
+        local "$1" && mo::indirect "$1" "the value"
+    }
+    callFunc dest
+    echo "$dest"  # writes "the value"
+
+Returns nothing.
+
+
+`mo::indirectArray()`
+---------------------
+
+Internal: Send an array as a variable up to caller of a function
+
+* $1 - Variable name
+* $2-@ - Array elements
+
+Examples
+
+    callFunc () {
+        local myArray=(one two three)
+        local "$1" && mo::indirectArray "$1" "${myArray[@]}"
+    }
+    callFunc dest
+    echo "${dest[@]}" # writes "one two three"
+
+Returns nothing.
+
+
+`mo::trimUnparsed()`
+--------------------
+
+Internal: Trim leading characters from MO_UNPARSED
+
+Returns nothing.
+
+
+`mo::chomp()`
+-------------
+
+Internal: Remove whitespace and content after whitespace
+
+* $1 - Name of the destination variable
+* $2 - The string to chomp
+
+Returns nothing.
+
+
+`mo::parse()`
+-------------
+
+Public: Parses text, interpolates mustache tags. Utilizes the current value of MO_OPEN_DELIMITER, MO_CLOSE_DELIMITER, and MO_STANDALONE_CONTENT. Those three variables shouldn't be changed by user-defined functions.
+
+* $1 - Destination variable name - where to store the finished content
+* $2 - Content to parse
+* $3 - Preserve standalone status/content - truthy if not empty. When set to a value, that becomes the standalone content value
+
+Returns nothing.
+
+
+`mo::parseInternal()`
+---------------------
+
+Internal: Parse MO_UNPARSED, writing content to MO_PARSED. Interpolates mustache tags.
+
+No arguments
+
+Returns nothing.
+
+
+`mo::parseBlock()`
+------------------
+
+Internal: Handle parsing a block
+
+* $1 - Invert condition ("true" or "false")
+
+Returns nothing
+
+
+`mo::parseBlockFunction()`
+--------------------------
+
+Internal: Handle parsing a block whose first argument is a function
+
+* $1 - Invert condition ("true" or "false")
+* $2-@ - The parsed tokens from inside the block tags
+
+Returns nothing
+
+
+`mo::parseBlockArray()`
+-----------------------
+
+Internal: Handle parsing a block whose first argument is an array
+
+* $1 - Invert condition ("true" or "false")
+* $2-@ - The parsed tokens from inside the block tags
+
+Returns nothing
+
+
+`mo::parseBlockValue()`
+-----------------------
+
+Internal: Handle parsing a block whose first argument is a value
+
+* $1 - Invert condition ("true" or "false")
+* $2-@ - The parsed tokens from inside the block tags
+
+Returns nothing
+
+
+`mo::parsePartial()`
+--------------------
+
+Internal: Handle parsing a partial
+
+No arguments.
+
+Indentation will be applied to the entire partial's contents before parsing. This indentation is based on the whitespace that ends the previously parsed content.
+
+Returns nothing
+
+
+`mo::parseComment()`
+--------------------
+
+Internal: Handle parsing a comment
+
+No arguments.
+
+Returns nothing
+
+
+`mo::parseDelimiter()`
+----------------------
+
+Internal: Handle parsing the change of delimiters
+
+No arguments.
+
+Returns nothing
+
+
+`mo::parseValue()`
+------------------
+
+Internal: Handle parsing value or function call
+
+No arguments.
+
+Returns nothing
+
+
+`mo::isFunction()`
+------------------
+
+Internal: Determine if the given name is a defined function.
+
+* $1 - Function name to check
+
+Be extremely careful.  Even if strict mode is enabled, it is not honored in newer versions of Bash.  Any errors that crop up here will not be caught automatically.
+
+Examples
+
+    moo () {
+        echo "This is a function"
+    }
+    if mo::isFunction moo; then
+        echo "moo is a defined function"
+    fi
+
+Returns 0 if the name is a function, 1 otherwise.
+
+
+`mo::isArray()`
+---------------
+
+Internal: Determine if a given environment variable exists and if it is an array.
+
+* $1 - Name of environment variable
+
+Be extremely careful.  Even if strict mode is enabled, it is not honored in newer versions of Bash.  Any errors that crop up here will not be caught automatically.
+
+Examples
+
+    var=(abc)
+    if moIsArray var; then
+       echo "This is an array"
+       echo "Make sure you don't accidentally use \$var"
+    fi
+
+Returns 0 if the name is not empty, 1 otherwise.
+
+
+`mo::isArrayIndexValid()`
+-------------------------
+
+Internal: Determine if an array index exists.
+
+* $1 - Variable name to check
+* $2 - The index to check
+
+Has to check if the variable is an array and if the index is valid for that type of array.
+
+Returns true (0) if everything was ok, 1 if there's any condition that fails.
+
+
+`mo::isVarSet()`
+----------------
+
+Internal: Determine if a variable is assigned, even if it is assigned an empty value.
+
+* $1 - Variable name to check.
+
+Can not use logic like this in case invalid variable names are passed.      [[ "${!1-a}" == "${!1-b}" ]]
+
+Returns true (0) if the variable is set, 1 if the variable is unset.
+
+
+`mo::isTruthy()`
+----------------
+
+Internal: Determine if a value is considered truthy.
+
+* $1 - The value to test
+* $2 - Invert the value, either "true" or "false"
+
+Returns true (0) if truthy, 1 otherwise.
+
+
+`mo::evaluate()`
+----------------
+
+Internal: Convert token list to values
+
+* $1 - Destination variable name
+* $2-@ - Tokens to convert
+
+Sample call:
+
+      mo::evaluate dest NAME username VALUE abc123 PAREN 2
+
+Returns nothing.
+
+
+`mo::evaluateListOfSingles()`
+-----------------------------
+
+Internal: Convert an argument list to individual values.
+
+* $1 - Destination variable name
+* $2-@ - A list of argument types and argument name/value.
+
+This assumes each value is separate from the rest. In contrast, mo::evaluate will pass all arguments to a function if the first value is a function.
+
+Sample call:
+
+      mo::evaluateListOfSingles dest NAME username VALUE abc123
+
+Returns nothing.
+
+
+`mo::evaluateSingle()`
+----------------------
+
+Internal: Evaluate a single argument
+
+* $1 - Name of variable for result
+* $2 - Type of argument, either NAME or VALUE
+* $3 - Argument
+
+Returns nothing
+
+
+`mo::evaluateKey()`
+-------------------
+
+Internal: Return the value for @key based on current's name
+
+* $1 - Name of variable for result
+
+Returns nothing
+
+
+`mo::evaluateVariable()`
+------------------------
+
+Internal: Handle a variable name
+
+* $1 - Destination variable name
+* $2 - Variable name
+
+Returns nothing.
+
+
+`mo::findVariableName()`
+------------------------
+
+Internal: Find the name of a variable to use
+
+* $1 - Destination variable name, receives an array
+* $2 - Variable name from the template
+
+The array contains the following values
+    * [0] - Variable name
+    * [1] - Array index, or empty string
+
+Example variables      a="a"
+      b="b"
+      c=("c.0" "c.1")
+      d=([b]="d.b" [d]="d.d")
+
+Given these inputs (function input, current value), produce these outputs      a c => a
+      a c.0 => a
+      b d => d.b
+      b d.d => d.b
+      a d => d.a
+      a d.d => d.a
+      c.0 d => c.0
+      d.b d => d.b
+      '' c => c
+      '' c.0 => c.0
+ Returns nothing.
+
+
+`mo::join()`
+------------
+
+Internal: Join / implode an array
+
+* $1    - Variable name to receive the joined content
+* $2    - Joiner
+* $3-@ - Elements to join
+
+Returns nothing.
+
+
+`mo::evaluateFunction()`
+------------------------
+
+Internal: Call a function.
+
+* $1 - Variable for output
+* $2 - Content to pass
+* $3 - Function to call
+* $4-@ - Additional arguments as list of type, value/name
+
+Returns nothing.
+
+
+`mo::standaloneCheck()`
+-----------------------
+
+Internal: Check if a tag appears to have only whitespace before it and after it on a line. There must be a new line before and there must be a newline after or the end of a string
+
+No arguments.
+
+Returns 0 if this is a standalone tag, 1 otherwise.
+
+
+`mo::standaloneProcess()`
+-------------------------
+
+Internal: Process content before and after a tag. Remove prior whitespace up to the previous newline. Remove following whitespace up to and including the next newline.
+
+No arguments.
+
+Returns nothing.
+
+
+`mo::indentLines()`
+-------------------
+
+Internal: Apply indentation before any line that has content in MO_UNPARSED.
+
+* $1 - Destination variable name.
+* $2 - The indentation string.
+* $3 - The content that needs the indentation string prepended on each line.
+
+Returns nothing.
+
+
+`mo::escape()`
+--------------
+
+Internal: Escape a value
+
+* $1 - Destination variable name
+* $2 - Value to escape
+
+Returns nothing
+
+
+`mo::getContentUntilClose()`
+----------------------------
+
+Internal: Get the content up to the end of the block by minimally parsing and balancing blocks. Returns the content before the end tag to the caller and removes the content + the end tag from MO_UNPARSED. This can change the delimiters, adjusting MO_OPEN_DELIMITER and MO_CLOSE_DELIMITER.
+
+* $1 - Destination variable name
+* $2 - Token string to match for a closing tag
+
+Returns nothing.
+
+
+`mo::tokensToString()`
+----------------------
+
+Internal: Convert a list of tokens to a string
+
+* $1 - Destination variable for the string
+* $2-$@ - Token list
+
+Returns nothing.
+
+
+`mo::getContentTrim()`
+----------------------
+
+Internal: Trims content from MO_UNPARSED, returns trimmed content.
+
+* $1 - Destination variable
+
+Returns nothing.
+
+
+`mo::getContentComment()`
+-------------------------
+
+Get the content up to and including a close tag
+
+* $1 - Destination variable
+
+Returns nothing.
+
+
+`mo::getContentDelimiter()`
+---------------------------
+
+Get the content up to and including a close tag. First two non-whitespace tokens become the new open and close tag.
+
+* $1 - Destination variable
+
+Returns nothing.
+
+
+`mo::getContentWithinTag()`
+---------------------------
+
+Get the content up to and including a close tag. First two non-whitespace tokens become the new open and close tag.
+
+* $1 - Destination variable, an array
+* $2 - Terminator string
+
+The array contents:      [0] The raw content within the tag
+      [1] The parsed tokens as a single string
+
+Returns nothing.
+
+
+`mo::tokenizeTagContents()`
+---------------------------
+
+Internal: Parse MO_UNPARSED and retrieve the content within the tag delimiters. Converts everything into an array of string values.
+
+* $1 - Destination variable for the array of contents.
+* $2 - Stop processing when this content is found.
+
+The list of tokens are in RPN form. The first item in the resulting array is the number of actual tokens (after combining command tokens) in the list.
+
+Given: a 'bc' "de\"\n" (f {g 'h'}) Result: ([0]=4 [1]=NAME [2]=a [3]=VALUE [4]=bc [5]=VALUE [6]=$'de\"\n' [7]=NAME [8]=f [9]=NAME [10]=g [11]=VALUE [12]=h [13]=BRACE [14]=2 [15]=PAREN [16]=2
+
+Returns nothing
+
+
+`mo::tokenizeTagContentsName()`
+-------------------------------
+
+Internal: Get the contents of a variable name.
+
+* $1 - Destination variable name for the token list (array of strings)
+
+Returns nothing
+
+
+`mo::tokenizeTagContentsDoubleQuote()`
+--------------------------------------
+
+Internal: Get the contents of a tag in double quotes. Parses the backslash sequences.
+
+* $1 - Destination variable name for the token list (array of strings)
+
+Returns nothing.
+
+
+`mo::tokenizeTagContentsSingleQuote()`
+--------------------------------------
+
+Internal: Get the contents of a tag in single quotes. Only gets the raw value.
+
+* $1 - Destination variable name for the token list (array of strings)
+
+Returns nothing.
+
+
+`MO_ORIGINAL_COMMAND`
+---------------------
+
+Save the original command's path for usage later
+
+
+[mo]: ./mo
+[tomdoc.sh]: https://github.com/tests-always-included/tomdoc.sh

vendor/git.knownelement.com/ExternalVendorCode/mo/Dockerfile

@@ -0,0 +1,7 @@
+FROM alpine
+
+RUN apk add --no-cache bash
+ADD mo /usr/local/bin/mo
+RUN chmod +x /usr/local/bin/mo
+
+ENTRYPOINT /usr/local/bin/mo

vendor/git.knownelement.com/ExternalVendorCode/mo/LICENSE.md

@@ -0,0 +1,7 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.
+
+The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed  by contributors", in the same place and form as other third-party acknowledgments. Alternately, this acknowledgment may appear in the software itself, in the same form and location as other such third-party acknowledgments.

vendor/git.knownelement.com/ExternalVendorCode/mo/README.md

@@ -0,0 +1,340 @@
+Mo - Mustache Templates in Bash
+===============================
+
+[Mustache] templates are simple, logic-less templates.  Because of their simplicity, they are able to be ported to many languages.  The syntax is quite simple.
+
+    Hello, {{NAME}}.
+
+    I hope your {{TIME_PERIOD}} was fun.
+
+The above file is [`demo/fun-trip.mo`](demo/fun-trip.mo).  Let's try using this template some data from bash's environment.  Go to your checked out copy of the project and run a command like this:
+
+    NAME=Tyler TIME_PERIOD=weekend ./mo demo/fun-trip.mo
+
+Your result?
+
+    Hello, Tyler.
+
+    I hope your weekend was fun.
+
+This bash version supports conditionals, functions (both as filters and as values), as well as indexed arrays (for iteration).  You are able to leverage these additional features by adding more information into the environment.  It is easiest to do this when you source `mo`.  See the [demo scripts](demo/) for further examples.
+
+
+Requirements
+------------
+
+* Bash 3.x (the aim is to make it work on Macs)
+* The "coreutils" package (`basename` and `cat`)
+* ... that's it.  Why?  Because bash **can**!
+
+If you intend to develop this and run the official specs, you also need node.js.
+
+
+Installation
+------------
+
+There are a few ways you can install this tool.  How you install it depends on how you want to use it.
+
+
+### Globally; For Everyone
+
+You can install this file in `/usr/local/bin/` or `/usr/bin/` by simply downloading it, changing the permissions, then moving it to the right location.  Double check that your system's PATH includes the destination folder, otherwise users may have a hard time starting the command.
+
+    # Download
+    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
+
+    # Make executable
+    chmod +x mo
+
+    # Move to the right folder
+    sudo mv mo /usr/local/bin/
+
+    # Test
+    echo "works" | mo
+
+
+### Locally; For Yourself
+
+This is very similar to installing it globally but it does not require root privileges.  It is very important that your PATH includes the destination folder otherwise it won't work.  Some local folders that are typically used are `~/bin/` and `~/.local/bin/`.
+
+    # Download
+    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
+
+    # Make executable
+    chmod +x mo
+
+    # Ensure destination folder exists
+    mkdir -p ~/.local/bin/
+
+    # Move to the right folder
+    mv mo ~/.local/bin/
+
+    # Test
+    echo "works" | mo
+
+
+### As A Library; For A Tool
+
+Bash scripts can source `mo` to include the functionality in their own routines.  This usage typically would have `mo` saved to a `lib/` folder in an application and your other scripts would use `. lib/mo` to bring it into your project.
+
+    # Download
+    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
+
+    # Move into your project folder
+    mv mo ~/projects/amazing-things/lib/
+
+To allow it to work this way, you either should source the file (`. "lib/mo"`) or make it executable (`chmod +x lib/mo`) and run it from your scripts.
+
+
+How to Use
+----------
+
+If you only plan using strings and numbers, nothing could be simpler.  In your shell script you can choose to export the variables.  The below script is [`demo/using-strings`](demo/using-strings).
+
+    #!/usr/bin/env bash
+    cd "$(dirname "$0")" # Go to the script's directory
+    export TEST="This is a test"
+    echo "Your message:  {{TEST}}" | ../mo
+
+The result?  "Your message:  This is a test".
+
+Using arrays adds a slight level of complexity.  *You must source `mo`.*  Look at [`demo/using-arrays`](demo/using-arrays).
+
+    #!/usr/bin/env bash
+    cd "$(dirname "$0")" # Go to the script's directory
+    export ARRAY=( one two "three three three" four five )
+    . ../mo # This loads the "mo" function
+    cat << EOF | mo
+    Here are the items in the array:
+    {{#ARRAY}}
+        * {{.}}
+    {{/ARRAY}}
+    EOF
+
+The result?  You get a list of the five elements in the array.  It is vital that you source `mo` and run the function when you want arrays to work because you can not execute a command and have arrays passed to that command's environment.  Instead, we first source the file to load the function and then run the function directly.
+
+There are more scripts available in the [demos directory](demo/) that could help illustrate how you would use this program.
+
+There are additional features that the program supports. Try using `mo --help` to see what is available.
+
+Please note that this command is written in Bash and pulls data from either the environment or (when using `--source`) from a text file that will be sourced and loaded into the environment, which means you will need to have Bash-style variables defined. Please see the examples in `demo/` for different ways you can use `mo`.
+
+
+Enhancements
+------------
+
+In addition to many of the features built-in to Mustache, `mo` includes a number of unique features that make it a bit more powerful.
+
+### Loop @key
+
+`mo` implements Handlebar's `@key` references for outputting the key inside of a loop:
+
+Env:
+```bash
+myarr=( foo bar )
+
+# Bash v4+
+declare -A myassoc
+myassoc[hello]="mo"
+myassoc[world]="is great"
+```
+
+Template:
+```handlebars
+{{#myarr}}
+ - {{@key}} {{.}}
+{{/myarr}}
+
+{{#myassoc}}
+ * {{@key}} {{.}}
+{{/myassoc}}
+```
+
+Output:
+```markdown
+ - 0 foo
+ - 1 bar
+
+ * hello mo
+ * world is great
+```
+
+
+### Helpers / Function Arguments
+
+Function Arguments are not a part of the official Mustache implementation, and are more often associated with Handlebar's Helper functionality.
+
+`mo` allows for passing strings to functions.
+
+```handlebars
+{{myfunc foo bar}}
+```
+
+For security reasons, these arguments are not immediately available to function calls without a flag.
+
+#### with `--allow-function-arguments`
+
+```bash
+myfunc() {
+    # Outputs "foo, bar"
+    echo "$1, $2";
+}
+```
+
+#### Using `$MO_FUNCTION_ARGS`
+
+```bash
+myfunc() {
+    # Outputs "foo, bar"
+    echo "${MO_FUNCTION_ARGS[0]}, ${MO_FUNCTION_ARGS[1]}";
+}
+```
+
+### Triple Mustache, Parenthesis, and Quotes
+
+Normally, triple mustache syntax, such as `{{{var}}}` will avoid HTML escaping of the variable. Because HTML escaping is not supported in `mo`, this is now used differently. Anything within braces will be looked up and the values will be concatenated together and the result will be treated as a value. Anything in parenthesis will be looked up, concatenated, and treated as a name. Also, anything in single quotes is passed as a value; double quoted things first are unescaped and then passed as a value.
+
+```
+# Example input
+var=abc
+user=admin
+admin=Administrator
+u=user
+abc=([0]=zero [1]=one [2]=two)
+```
+
+| Mustache syntax | Resulting output | Notes |
+|-----------------|------------------|-------|
+| `{{var}}` | `abc` | Normal behavior |
+| `{{var us}}` | `abcus` | Concatenation |
+| `{{'var'}}` | `var` | Passing as a value |
+| `{{"a\tb"}}` | `a       b` | There was an escaped tab in the value |
+| `{{u}}` | `user` | Normal behavior |
+| `{{{u}}}` | `user` | Look up "$u", treat as the value `{{'user'}}` |
+| `{{(u)}}` | `admin` | Look up "$u", treat as the name `{{user}}` |
+| `{{var user}}` | `abcuser` | Concatenation |
+| `{{(var '.1')}}` | `one` | Look up "$var", treat as "abc", then concatenate ".1" and look up `{{abc.1}}` |
+
+In double-quoted strings, the following escape sequences are defined.
+
+* `\"` - Quote
+* `\b` - Bell
+* `\e` - Escape (note that Bash typically uses $'\E' for the same thing)
+* `\f` - Form feed
+* `\n` - Newline
+* `\r` - Carriage return
+* `\t` - Tab
+* `\v` - Vertical tab
+* Anything else will skip the `\` and place the next character. However, this implementation is allowed to change in the future if a different escape character mapping becomes commonplace.
+
+
+Environment Variables and Functions
+-----------------------------------
+
+There are several functions and variables used to process templates. `mo` reserves variables that start with `MO_` for variables exposing data or configuration, functions starting with `mo::`, and local variables starting with `mo[A-Z]`. You are welcome to use internal functions, though only ones that are marked as "Public" should not change their interface. Scripts may also read any of the variables.
+
+Functions are all executed in a subshell, with another subshell for lambdas. Thus, your lambda can't affect the parsing of a template. There's more information about lambdas when talking about tests that fail.
+
+* `MO_ALLOW_FUNCTION_ARGUMENTS` - When set to a non-empty value, this allows functions referenced in templates to receive additional options and arguments.
+* `MO_CLOSE_DELIMITER` - The string used when closing a tag. Defaults to "}}". Used internally.
+* `MO_CLOSE_DELIMITER_DEFAULT` - The default value of `MO_CLOSE_DELIMITER`. Used when resetting the close delimiter, such as when parsing a partial.
+* `MO_CURRENT` - Variable name to use for ".".
+* `MO_DEBUG` - When set to a non-empty value, additional debug information is written to stderr.
+* `MO_FUNCTION_ARGS` - Arguments passed to the function.
+* `MO_FAIL_ON_FILE` - If a filename from the command-line is missing or a partial does not exist, abort with an error.
+* `MO_FAIL_ON_FUNCTION` - If a function returns a non-zero status code, abort with an error.
+* `MO_FAIL_ON_UNSET` - When set to a non-empty value, expansion of an unset env variable will be aborted with an error.
+* `MO_FALSE_IS_EMPTY` - When set to a non-empty value, the string "false" will be treated as an empty value for the purposes of conditionals.
+* `MO_OPEN_DELIMITER` - The string used when opening a tag. Defaults to "{{". Used internally.
+* `MO_OPEN_DELIMITER_DEFAULT` - The default value of MO_OPEN_DELIMITER. Used when resetting the open delimiter, such as when parsing a partial.
+* `MO_ORIGINAL_COMMAND` - Used to find the `mo` program in order to generate a help message.
+* `MO_PARSED` - Content that has made it through the template engine.
+* `MO_STANDALONE_CONTENT` - The unparsed content that preceeded the current tag. When a standalone tag is encountered, this is checked to see if it only contains whitespace. If this and the whitespace condition after a tag is met, then this will be reset to $'\n'.
+* `MO_UNPARSED` - Template content yet to make it through the parser.
+
+
+Concessions
+-----------
+
+I admit that implementing everything in bash just doesn't make a lot of sense.  For example, the following things just don't work because they don't really mesh with the "bash way".
+
+Pull requests to solve the following issues would be helpful.
+
+
+### Mustache Syntax
+
+* Dotted names are supported but only for associative arrays (Bash 4).  See [`demo/associative-arrays`](demo/associative-arrays) for an example.
+* There's no "top level" object, so `echo '{{.}}' | ./mo` does not do anything useful.  In other languages you can say the data for the template is a string and in `mo` the data is always the environment.  Luckily this type of usage is rare and `{{.}}` works great when iterating over an array.
+* [Parents](https://mustache.github.io/mustache.5.html#Parents), where a template can override chunks of a partial, are not supported.
+* HTML encoding is not built into `mo`.  `{{{var}}}`, `{{&var}}` and `{{var}}` all do the same thing.  `echo '{{TEST}}' | TEST='<b>' mo` will give you "`<b>`" instead of "`&gt;b&lt;`".
+
+
+### General Scripting Issues
+
+* Using binary files as templates is simply not allowed.
+* Bash does not support anything more complex than strings/numbers inside of associative arrays.  I'm not able to add objects nor nested arrays to bash - it's just a shell after all!
+* You must make sure the data is in the environment when `mo` runs.  The easiest way to do that is to source `mo` in your shell script after setting up lots of other environment variables / functions.
+
+
+Developing
+----------
+
+Check out the code and hack away.  Please add tests to show off bugs before fixing them.  New functionality should also be covered by a test.
+
+First, make sure you install Node.js. After that, run `npm run install-tests` to get the dependencies and the repository of YAML tests. Run `npm run test` to run the JavaScript tests. There's over 100 of them, which is great. Not all of them will pass, but that's discussed later.
+
+When submitting patches, make sure to run them past [ShellCheck] and ensure no problems are found.  Also please use Bash 3 syntax if you are manipulating arrays.
+
+
+### Porting and Backporting
+
+In case of problems, setting MO_DEBUG to a non-empty value will give you LOTS of output.
+
+    MO_DEBUG=1 ./mo my-template
+
+
+### Failed Specs
+
+It is acceptable for some of the official spec tests to fail. The spec runner has specific exclusions and overrides to test similar functionality that avoid the following issues.
+
+ * Using `{{.}}` outside of a loop - In order to access any variable, you must use its name. In a loop, `{{.}}` will refer to the current value, but outside the loop you are unable to use this dot notation because there is no current value.
+ * Deeply nested data - Bash doesn't support complex data structure. Basically, just strings and arrays of strings.
+ * Interpolation; Multiple Calls:  This fails because lambdas execute in a subshell so their output can be captured. If you want state to be preserved, you will need to write it outside of the current environment and load it again later.
+ * HTML Escaping - Since bash is not often executed in a web server context, it makes no sense to have the output escaped as HTML.  Performing shell escaping of variables may be an option in the future if there's a demand.
+ * Lambdas - Function results are *not* automatically interpreted again. If you want to parse the results as Mustache content, use `mo::parse`. When they use `mo::parse`, it will use the current delimiters.
+
+ For lambdas, these examples may help.
+
+ ```bash
+ # Retrieve content into a variable.
+ content=$(cat)
+
+ # Retrieve all content and do not trim newlines at the end.
+ content=$(cat; echo -n '.')
+ content=${content%.}
+
+ # Parse content using the current delimiters
+ mo::parse results "This is my content. Hello, {{username}}"
+ echo -n "$results"
+
+ # Parse content using the default delimiters
+ MO_OPEN_DELIMITER=$MO_OPEN_DELIMITER_DEFAULT
+ MO_CLOSE_DELIMITER=$MO_CLOSE_DELIMITER_DEFAULT
+ mo::parse results "This is my content. Hello, {{username}}"
+ echo -n "$results"
+ ```
+
+
+### Future Enhancements
+
+There's a few places in the code marked with `TODO` to signify areas that could use improvement.  Care to help?  Keep in mind that this uses bash exclusively, so it might not look the prettiest.
+
+
+License
+-------
+
+This program is licensed under an MIT license with an additional non-advertising clause.  See [LICENSE.md](LICENSE.md) for the full text.
+
+
+[Mustache]: https://mustache.github.io/
+[ShellCheck]: https://github.com/koalaman/shellcheck

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/associative-arrays

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+declare -A DATA
+export DATA=([one]=111 [two]=222)
+. ../mo
+
+cat <<EOF | mo
+Accessing data directly:
+    DATA: {{DATA}}
+    One: {{DATA.one}}
+    Two: {{DATA.two}}
+
+Things in DATA:
+{{#DATA}}
+    Item: {{.}}
+{{/DATA}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/embedded-template

@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+#
+# This embeds a template in the script without using strange `cat` syntax.
+# shellcheck disable=SC1083 disable=SC1010 disable=SC1054 disable=SC1073 disable=SC1072 disable=SC1056 disable=SC1009
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+export NAME="Tyler"
+export VEHICLE="Ford Explorer"
+export OVERDUE_LENGTH="2 months"
+export OPTIONS=(
+    "Call a service representative at 1-800-000-0000 to discuss payment options"
+    "Return the vehicle immediately and pay a fine of 1 million dollars"
+)
+. ../mo
+sed '0,/^# END/ d' "$(basename "$0")" | mo
+exit
+
+# END
+Attention {{NAME}},
+
+You need to pay for the {{VEHICLE}} you are leasing from us.
+It has been {{OVERDUE_LENGTH}} since your last payment.
+At this point you must do one of the following:
+
+{{#OPTIONS}}
+ * {{.}}
+{{/OPTIONS}}

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/fun-trip.mo

@@ -0,0 +1,3 @@
+Hello, {{NAME}}
+
+I hope your {{TIME_PERIOD}} was fun.

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args

@@ -0,0 +1,31 @@
+#!/usr/bin/env bash
+#
+# This sources a simple script with the env. variables needed for the template.
+
+cd "$(dirname "$0")" # Go to the script's directory
+source ../mo
+
+export NAME="Alex"
+export ARRAY=( AAA BBB CCC )
+
+# Include an external template
+INCLUDE() {
+    # shellcheck disable=SC2031
+    cat "${MO_FUNCTION_ARGS[0]}"
+}
+
+# Print section title
+TITLE() {
+    echo "+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+"
+    # shellcheck disable=SC2031
+    echo "${MO_FUNCTION_ARGS[0]}"
+    echo "+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+"
+}
+
+cat <<EOF | mo -u
+{{TITLE 'Part 1'}}
+{{INCLUDE 'function-args-part1'}}
+
+{{TITLE 'Part 2'}}
+{{INCLUDE 'function-args-part2'}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part1

@@ -0,0 +1 @@
+Hello, my name is {{NAME}}.

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part2

@@ -0,0 +1,3 @@
+{{#ARRAY}}
+    * {{.}}
+{{/ARRAY}}

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-advanced-looping

@@ -0,0 +1,42 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+EVERY_REPO() {
+    # The block contents come in through standard input. Capture it here.
+    content=$(cat)
+
+    echo "# Starting EVERY_REPO"
+
+    # Get list of repos
+    for REPO in "${REPOS[@]}"; do
+        echo "## Looping one time for repo: $REPO"
+
+        # String replace REPO_ with the name
+        # This changes everything in the content block of the template.
+        # It rewrites {{__REPO__.name}} into {{resque.name}}, for instance.
+        # You can prefix your environment variables and do other things as well.
+        
+        echo "$content" | sed "s/__REPO__/${REPO}/"
+
+        echo "## Looped one time for repo: $REPO"
+    done
+
+    echo "# Finished EVERY_REPO"
+}
+
+REPOS=(resque hub rip)
+
+declare -A resque hub rip
+resque=([name]=Resque [url]=http://example.com/resque)
+hub=([name]=Hub [url]=http://example.com/hub)
+rip=([name]=Rip [url]=http://example.com/rip)
+. ../mo
+cat <<EOF | mo
+{{#EVERY_REPO}}
+The repo is __REPO__
+    Name:  {{__REPO__.name}}
+    URL:  {{__REPO__.url}}
+{{/EVERY_REPO}}
+
+EOF