Anton Kvashenkin jugatsu

This has been moved into the official Chef docs:

12.5 style custom resources

This is by far the most recommended way of writing resources for all users. There are two gotchas which we're working through:

For helper functions that you used to write in your provider code or used to mixin to your provider code, you have to use an action_class do ... end block.

	[alias]
	pr = "!f() { git fetch origin pull/$1/head:sethvargo/pr-$1 && git checkout sethvargo/pr-$1; }; f"
	unreleased = "!f() { git fetch --tags && git diff $(git tag \| tail -n 1); }; f"
	up = "!f() { git fetch --all; git pull origin HEAD; for upstream in $(git remote); do git remote prune "${upstream}"; done }; f"
	graph = "!f() { git log --oneline --abbrev-commit --graph --decorate; }; f"
	undo = !git reset HEAD~1 --mixed
	amend = !git commit --amend --no-edit
	top = !git log --format=format:%an \| sort \| uniq -c \| sort -r \| head -n 20
	x = "!f() { gitx; }; f"

	###################################################
	##
	## Alertmanager YAML configuration for routing.
	##
	## Will route alerts with a code_owner label to the slack-code-owners receiver
	## configured above, but will continue processing them to send to both a
	## central Slack channel (slack-monitoring) and PagerDuty receivers
	## (pd-warning and pd-critical)
	##

	#!/bin/sh
	# Launch a Pod ab-using a hostPath mount to land on a Kubernetes node cluster as root
	# without requiring `privileged: true`, in particular can abuse `DenyExecOnPrivileged`
	# admission controller.
	# Pod command in turn runs a privileged container using node's /var/run/docker.sock.
	node=${1}
	case "${node}" in
	"")
	nodeSelector=''
	podName=${USER+${USER}-}docker-any

	<configuration>
	<appender name="STDERR" class="ch.qos.logback.core.ConsoleAppender">
	<target>System.err</target>
	<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
	<level>WARN</level>
	</filter>
	<encoder>
	<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
	</encoder>
	</appender>

	Some notes from engineering.

	1) Identify the partition

	Mnesia('rabbit@juju-machine-30-lxd-11'): ERROR mnesia_event got {inconsistent_database, running_partitioned_network, 'rabbit@juju-machine-29-lxd-9'}

	$ sudo rabbitmqctl cluster_status

	2) Pick the most reliable node as the master.

	#!/bin/sh
	docker images --format '{{.Size}}\t{{.Repository}}\t{{.Tag}}\t{{.ID}}' \| sed 's/ //' \| sort -h -r \| column -t

	cd F:\PostgreSQL\9.6\data

	psql -U postgres -d devel -W -c "SELECT pg_start_backup('BK 20161120');";

	-- in cmd (node the last dot in command)
	"C:\Program Files\Java\jdk1.8.0_74\bin\jar.exe" cvf F:/backup/data_20161118.zip -C "F:/PostgreSQL/9.6/data" .
	-- in powershell (node the first ampersand and the last dot in command)
	& 'C:\Program Files\Java\jdk1.8.0_74\bin\jar.exe' cvf F:/backup/data_20161118.zip -C "F:/PostgreSQL/9.6/data" .

	psql -U postgres -d devel -W -c "SELECT pg_xlogfile_name(pg_stop_backup());"