Skip to content

Instantly share code, notes, and snippets.

Writing YAML + HCL and googling errors

Julien Bisconti veggiemonk

Writing YAML + HCL and googling errors
Block or report user

Report or block veggiemonk

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View .zsh_alias
alias ez="vim ~/.zshrc && source ~/.zshrc"
alias c="clear"
alias path='echo -e ${PATH//:/\\n}'
alias dpsa="docker ps -a"
alias dcup="docker-compose up"
alias dcupd="docker-compose up -d"
alias dcdn="docker-compose down"
alias dclf="docker-compose logs -f"
alias server="python3 -m http.server"



mkdir -p $HOME/bin
cd $HOME/bin
export PATH="$PATH:$HOME/bin"
veggiemonk / main.go
Created May 17, 2019
forseti-viz server in csv
View main.go
package main
import (
# Specify the name of the kubernetes context that has permissions to create the service account in your
# target cluster and namespace. To get the list of contexts, you can run "kubectl config get-contexts"
export CONTEXT="$(kubectl config current-context)"
# Enter the namespace that you want to install Spinnaker in. This can already exist, or can be created.
export NAMESPACE="spinnaker"
# Enter the name of the service account you want to create. This will be created in the target namespace
export SERVICE_ACCOUNT_NAME="spinnaker"
cd ~
mkdir -p $HOME/bin
git clone ~/.kubectx
ln -s $HOME/.kubectx/kube $HOME/bin/
ln -s $HOME/.kubectx/kubectx $HOME/bin/
veggiemonk /
Last active Apr 2, 2019
git fixup autosquash workflow
# source
git add .
git commit --fixup HEAD
git rebase -i --autosquash HEAD~2
veggiemonk / get_jenkins_plugins.js
Created Apr 2, 2019
get all the plugins in jenkins
View get_jenkins_plugins.js
// run this in the web console when logged in
.map(x => [, x.querySelector('.excerpt').textContent])
veggiemonk /
Created Mar 29, 2019 — forked from anonymous/
Acronyms Seriously Suck - Elon Musk

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.

That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.

You can’t perform that action at this time.