Skip to content

Instantly share code, notes, and snippets.

View booninite's full-sized avatar

alex weidner booninite

View GitHub Profile
yarn run v1.15.2
$ /Users/shimmerjs/code/tmp/node_modules/.bin/webpack --config-register tsconfig-paths/register --config-name packages
Hash: 873bf5d0da749619fb00
Version: webpack 4.29.6
Time: 3423ms
Built at: 03/31/2019 6:11:04 PM
Asset Size Chunks Chunk Names
@bcs-infra/cli-logger.js 270 KiB @bcs-infra/cli-logger [emitted] @bcs-infra/cli-logger
@bcs-infra/config.js 910 KiB @bcs-infra/config [emitted] @bcs-infra/config
@bcs-infra/logger.js 2.2 MiB @bcs-infra/logger [emitted] @bcs-infra/logger
@booninite
booninite / ci.yaml
Created October 26, 2018 15:49
entrypoint for ci
templates:
- name: ci
dag:
tasks:
- name: setup
template: setup
- name: build-typescript
dependencies: [setup]
template: build-typescript
arguments:
@booninite
booninite / skaffold.yaml
Created July 15, 2018 19:08
example skaffold file for a monorepo that has images for web services and CLI docker images, using anchors to help maintainability
apiVersion: skaffold/v1alpha2
kind: Config
# default build profile builds every image in the repository without pushing
# used to verify build
build:
tagPolicy:
sha256: {}
artifacts:
- imageName: &grady registry.ng.bluemix.net/dev-infra/grady
# &ws -> "workspace"

friction when upgrading GKE Kubernetes cluster versions

  1. You can see update is available in GCP console for the master. Selecting it provides an array of options, including some containing -gke.1.
  2. You choose one of those options, await cluster upgrade, and notice your nodes are out of sync. Knowing you don't want nodes to stay out of sync long, you decide to go ahead and take care of it.
  3. You discover there is no way to update node version from the console. This is fine, and you find the documentation for the CLI command to do so. You attempt to upgrade it to the same version you chose for your master, including -gke.1. You get a 400 for bad version number.
  4. You look up supported versions for master and nodes. -gke.1 is not on the list for nodes.
  5. This is fine, you attempt to install the non -gke.1 version to get as close as you can to the master. gcloud tells you that you can only install versions to the node that explicitly match master.
  6. You say what in the fuck.

Keybase proof

I hereby claim:

  • I am booninite on github.
  • I am shimmerjs (https://keybase.io/shimmerjs) on keybase.
  • I have a public key ASCgoj7NJsoxRhrp31m2AslEKj_dW5ZrQpCfEtNLYWy2dQo

To claim this, I am signing this object:

process.env.NODE_ENV = 'development';
// use .env file instead of settings environment directly
require('dotenv').config({silent: true});
const chalk = require('chalk');
const webpack = require('webpack');
const checkRequiredFiles = require('react-dev-utils/checkRequiredFiles');
const formatWebpackMessages = require('react-dev-utils/formatWebpackMessages');
const bsync = require('browser-sync').create();
################################################################################
# git niceties
# branch and branch status
export GITAWAREPROMPT=~/.bash/git-aware-prompt
source $GITAWAREPROMPT/main.sh
# auto completion
if [ -f ~/.git-completion.bash ]; then
. ~/.git-completion.bash
fi