3.1.1

Enables HTTP basic auth via htpasswd on dbt reposerver.

3.1.0

Adds ability to load boilerplate templates from base64 encoded text.

To utilize, build like go build -ldflags "-X github.com/nikogura/dbt/pkg/dbt.METADATA_TEMPLATE=${METADATA_TEMPLATE}" to override included metadata template for producing metadata.json with dbt boilerplate gen.

Can be done via gomason >= 2.2.6 by including "-X github.com/nikogura/dbt/pkg/dbt.METADATA_TEMPLATE=${METADATA_TEMPLATE}" in each build target in metadata.json`

This method of customizing the boilerplate templates is crude, but is less involved than hacking the source code directly. It arguably will allow for easier maintenance of forks.

3.0.4

Install scripts should work better with password managers due to better variable names.

Apparently I'm not the only one who used $TMPDIR to hold a temporary directory.

1password, mktemp -d, and dbt's installer was conflicting leading to problems.

Who knew?

3.0.3

Added support for using S3 as a trusted repostiory.

3.0.2

This version adds an installer for basic auth leveraging the macOS Keychain.

It's not as secure as a full password manager (it doesn't time out, as long as you're logged in, you have access to the creds), but it's occasionally useful.

3.0.1

Enabled dbt to fetch basic auth credentials from a shell function if you're into that sort of thing.

3.0.0

Main change in v3.0.0 is a rework of the internals of dbt itself to use the cobra framework and allow for use of the -- construct to separate dbt's args from the tool dbt is running and the tools's arguments.

If your tool has no flagged arguments, you will see no changes.

If your tool has flags, you'll need to insert -- between dbt's flags and the name of your tool. e.g.:

Old: dbt foo -a bar
New: dbt -- foo -a bar

2.2.5

Changed dbt's internal version detection to use sha256 rather than sha1. It's more secure, and it matches what dbt does with tools. Yay consistency!

2.2.4

Faster timeouts if trusted repo is not available.

Clearer more helpful error messages.

2.2.3

Moved main.go from boilerplate generated code from /cmd//main.go to /main.go

While it's location under 'cmd' is more 'proper' from the perspective of the suggested golang project layout spec, it's confusing to new tool authors.

Running 'go build' with main.go doesn't work, and running go build ./... produces no binaries per go help build.