Brian bchumney

Customising the dbt-event-logging package

As of dbt-event-logging 0.6.0, the only customisation that can be done to it is to redefine the schema where the dbt_audit_log table is put into (see readme). If you want to further customise the columns that get's recorded in the dbt_audit_log table itself, for example adding dbt_cloud_run_id, you will have to get knee deep into the source macros.

To make thing's easier, we can just copy most of the code in the source audit.sql macro, put it in your macros folder (i.e. macros/audit.sql) and make some tweaks to it - this also means that you do not need to install the dbt-event-logging package via specifying it in your packages.yml file since the macro is part of our project.

The example audit.sql file in this gist shows how to add 2 additional c

Download docker-compose.yml to dir named sentry
Change SENTRY_SECRET_KEY to random 32 char string
Run docker-compose up -d
Run docker-compose exec sentry sentry upgrade to setup database and create admin user
(Optional) Run docker-compose exec sentry pip install sentry-slack if you want slack plugin, it can be done later
Run docker-compose restart sentry
Sentry is now running on public port 9000

https://docs.docker.com/compose/compose-file/#env_file

Instructions

Copy both files into the directory containing the files you want converted
Run excel-to-csv.bat

Note: This script requires Excel to be installed.

Drupal 8 Twig cheatsheet

Please note I created that sheet as a personal side note/draft and not everything is fully tested. There could be errors or better things to do. So if you spot something wrong or something that can be improved, feel free to comment below and I will do the changes.

Getting Drupal 8 field values in Twig

Image path: {{ file_url(content.field_name['#items'].entity.uri.value) }}

	# Use `%%capture` to hush 'noisy' stdout and stderr streams, but still combine with getting `%%time` after
	%%capture out_stream
	%%time
	---rest of a cell that does something with LOTS of output--
	#In cell after, put following to get time of completion from that:
	#time it took to run cell above
	for x in out_stream.stdout.split("\n")[-3:]:
	print(x)

	// all of this is made possible by the optimizely javascript api, specifically:
	// http://developers.optimizely.com/javascript/reference/#the-data-object
	function getExperiments() {
	var experimentInfo = {};
	var wasRedirected = false;

	/*
	* create an array of experiments that are active on the page
	* you must pass two tests to be placed in an active experiment:
	* 1) url targeting: https://help.optimizely.com/hc/en-us/articles/200040835-URL-Targeting-Choose-where-your-experiment-runs

	C!
	# Backends

	backend F_addr_api_example_com {
	.connect_timeout = 1s;
	.dynamic = true;
	.port = "443";
	.host = "api.example.com";
	.first_byte_timeout = 15s;
	.max_connections = 200;

	import csv
	import sys
	import os

	# example usage: python split.py example.csv 200
	# above command would split the `example.csv` into smaller CSV files of 200 rows each (with header included)
	# if example.csv has 401 rows for instance, this creates 3 files in same directory:
	# - `example_1.csv` (row 1 - 200)
	# - `example_2.csv` (row 201 - 400)
	# - `example_3.csv` (row 401)

	[alias]
	recent = "!git for-each-ref --sort=-committerdate refs/heads/ --format='%(committerdate:short) %(refname:short)' \| head -n 10"
	co = checkout
	cob = checkout -b
	coo = !git fetch && git checkout
	br = branch
	brd = branch -d
	brD = branch -D
	merged = branch --merged
	st = status

	'use strict';

	var mysqlBackup = require('./mysql-backup');
	var schedule = require('node-schedule');

	schedule.scheduleJob({ hour: 22, minute: 0 }, mysqlBackup);