bobhenkel

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

bobhenkel

Converge

Converge is a configuration management tool that makes it easy to manage servers, laptops and other devices.

• Easy to install and run.
• Includes a powerful graph engine that automatically generates dependencies and runs tasks in parallel.
• API-first. All communication runs through grpc.

bobhenkel

dash_id=xxxx
api_key=xxx
app_key=xxx

# 1. export
curl -X GET "https://app.datadoghq.com/api/v1/dash/${dash_id}?api_key=${api_key}&application_key=${app_key}" > dash.json

# 2. edit dash.json
move "graphs", "title", "description" up one level in the json hierarchy, from being beneath "dash" to being at the same level

bobhenkel

#!/bin/bash

# Outputs a pipeline that targets agents that have the same 'name' meta-data
# value as the step that does the pipeline upload. This means that all the
# steps will run on the same agent machine, assuming that the 'name' meta-data
# value is unique to each agent.
#
# Each agent needs to be configured with meta-data like so:
#
# meta-data="name=<unique-name>"

bobhenkel

Keybase proof

I hereby claim:

• I am bobhenkel on github.
• I am bobhenkel (https://keybase.io/bobhenkel) on keybase.
• I have a public key ASATsp7hpNkKlRnCBlXa_H3Y5cZL7mL5wzFWOpfBa6PtNQo

To claim this, I am signing this object:

bobhenkel

https://github.com/kubernetes-sigs/kubeadm-dind-cluster/issues/56

Run registry in docker on your host:
$ docker run -d -p 5000:5000 --restart=always --name registry registry:2
Now localhost:5000 is a registry url.

$ docker tag alpine:3.6 localhost:5000/alpine:3.6                                        
$ docker push localhost:5000/alpine:3.6     
...
3.6: digest: sha256:d6eda1410b93902ac84bdd775167c84ab59e5abadad88791d742fea93b161e93 size: 528

bobhenkel

https://coderwall.com/p/kucyaw/protect-secret-data-in-git-repo
'''
We use Ansible to manage our infrastructure, so a lot of configurations are stored in a git repository. Some of this configuration are potential dangerous if made public (like SSL certificate, GPG keys, ...) therefore we prefer to encrypt this data in the git repository.

To encode this data we use git-crypt.

Install git-crypt
Depending on your OS you need to install git-crypt, with homebrew is really simple:

brew install git-crypt

bobhenkel

#
# The header of the application manifest uses the same signature as a Kubernetes
# resource.
#
apiVersion: cluster.gravitational.io/v2
kind: Cluster
metadata:
  # The cluster name as shown to the end user, must be a single alphanumeric word
  name: MyCluster

bobhenkel

#
# The header of the application manifest uses the same signature as a Kubernetes
# resource.
#
apiVersion: cluster.gravitational.io/v2
kind: Cluster
metadata:
  # The cluster name as shown to the end user, must be a single alphanumeric word
  name: MyCluster

bobhenkel

curl -s https://api.github.com/orgs/twitter/repos?per_page=200 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}'