RichardBronosky

Shell Script Design Goals

• Don't avoid bashisms unless you know bash will be unavailable
  • Use #!/bin/bash rather than #!/bin/sh
  • If you are going to try to avoid bash, you must test on a system that does not have bash
• Always include a shebang #!
• Handle errors
  • Use set -eu (errexit & nounset)
• Sould be idemponent if read via source
  • Use subshells to avoid leaking unintended variables into the parent scope

RichardBronosky

#!/bin/bash -eu

[[ -z ${1:-} ]] && \
    echo -e "\n""Usage: $0 executable_path [destination_path] ""\n" || \
    executable_path="${1:-}"
: $executable_path
destination_path="${2:-/usr/local/bin}"

exec="$( basename $executable_path )"
dir="$(  dirname  $executable_path )"

RichardBronosky

Thu Nov 14 12:11:48 EST 2019

RichardBronosky

Thu Nov 14 12:10:38 EST 2019

RichardBronosky

Fork your own Gist

It used to be possible to fork your own gists via the browser using a little JS magic. This is no longer the case. As an alternative, you can use Chris Wanstrath's https://github.com/defunkt/gist cli tool to do the next best thing.

Usage

gist-fork git@gist.github.com:fcc543f7f1cfba404caf5ce276cc0951.git

RichardBronosky

Assume-Role

AWS Assume-Role requiring only aws-cli and jq

Installation

Basic

git clone https://gist.github.com/80306011bb5da80c765ffd6aa2ecf89b.git arole

RichardBronosky

rebase demo

RichardBronosky

Assume-Role

AWS Assume-Role requiring only aws-cli and jq

Installation

Basic

git clone https://gist.github.com/80306011bb5da80c765ffd6aa2ecf89b.git arole

RichardBronosky

#!/bin/bash -eu

pid_lineage(){
  ps -p ${1:-$$} -o pid,ppid,args | tail -n1 | \
    (
      read pid ppid args
      echo -e "$pid\t$args"
      [[ $pid -gt 1 ]] && pid_lineage $ppid -
    ) | (
      [[ ${2:-} != '-' ]] && \

RichardBronosky

Quick Start Guide for confd

from https://github.com/kelseyhightower/confd/blob/master/docs/quick-start-guide.md

Select a backend

I have selected for you. You are using the file backend. I found the original guide to be confusing because all the backend specifics were on one page and the scrolling made it hard to follow. Sometimes, less is more.

Install