yaml2json
Quick and dirty CLI tool for converting yaml
to json
.
example
[:~] 1 $ yaml2json <( echo -e '---\nfoo:\n- bar\n- baz' )
{
"foo": [
function password_from_keychain(service) | |
-- 'service' should be saved in the login keychain | |
local cmd = "/usr/bin/security 2>&1 >/dev/null find-generic-password -gs '" .. service .. "' | sed -En '/^password: / s,^password: \"(.*)\"$,\\1,p'" | |
local handle = io.popen(cmd) | |
local result = handle:read("*a") | |
handle:close() | |
return (result:gsub("^%s*(.-)%s*$", "%1")) | |
end |
Quick and dirty CLI tool for converting yaml
to json
.
[:~] 1 $ yaml2json <( echo -e '---\nfoo:\n- bar\n- baz' )
{
"foo": [
Shell script for downloading HashiCorp binaries.
Requires jq (brew install jq
) and gpg (brew cask install gpg-suite
).
I structure all my binaries as ~/devel/HashiCorp/binaries/<product>-<version>/<product>
and adjust paths as needed based on the project I'm working on.
#!/usr/bin/env python | |
# -*- encoding: utf-8 -*- | |
## clones a Go project into a new directory and sets up the workspace with direnv. | |
## | |
## example: | |
## $ go_clone git@github.com:hashicorp/nomad.git nomad | |
## | |
## * creates the "nomad" directory | |
## * creates a .envrc with "layout go" in it |
#!/usr/bin/env python | |
# -*- encoding: utf-8 -*- | |
## in order to cleanly shut down a node with running jobs, the node needs to be | |
## drained, and then we need to wait for allocations to be migrated away. in | |
## this script, we: | |
## * set up a watch for node-update evals for the current node | |
## * wait for allocations currently running to complete | |
## * wait for allocations from the watched evals to start running | |
## |
#!/bin/bash | |
set -e -u -o pipefail | |
{ | |
echo 'digraph G {' | |
brew list | while read cask; do | |
printf '"%s";\n' $cask | |
brew deps $cask | while read dep; do |
#!/usr/bin/env bash | |
## this is a total hack. acbuild needs systemd-nspawn. initially, I tried | |
## running the go agent in a rkt container, but failed for reasons I forget | |
## right now (overlayfs problems?). then I ran into more problems with systemd- | |
## nspawn on CentOS 7.1, and I forget the origin. we're getting closer: in | |
## CentOS 7.2 I'm able to run acbuild as root outside of a container. but when | |
## running within the go agent, systemd-nspawn is killed for no discernable | |
## reason. so, we're back to faking out acbuild by providing this systemd- | |
## nspawn-alike. |
I hereby claim:
To claim this, I am signing this object: