scripts

Documentation

Overview

This program uses the Evergreen REST API to grab the most recent configuration for each project and write each configuration file to the file system for further analysis. This program's purpose is to provide a useful utility that's too niche for the main CLI tool and provide a proof of concept to the REST API.

Usage: upon execution, this program will load the user's CLI settings

(default `~/.evergreen.yml`) and use them to download all project files
to the working directory in the form of "<project_id>.yml"

-c / --config can pass in a different CLI settings file

Archive

Provides a single "MakeTarball" function to create tar (tar.gz) archives. Uses go libraries rather than calling out to GNU tar or similar. Is more cross platform and makes it easy to prefix all contents inside of a directory that does not exist in the source.

The current vendoring solution supports both new and old style vendoring, via a trick: We commit all vendored code to the "vendor" directory, and then, if we're on a version/deployment of go that doesn't support new style vendoring, we symlink to "build/vendor/src" and add "build/vendor" to the gopath, which the render-gopath program generates inside of the makefile.

This script sets up the symlink. This is somewhat fragile for go1.5 and go1.6, if you change the value of the GO15VENDOREXPERIMENT environment variable, in between runs of "make-vendor" and builds. Similar switching between go1.4 environments and go1.6 will require manually rerunning this script.

Simple script to print the current GOPATH with additional vendoring component for legacy vendoring, as needed. Use in conjunction with makefile configuration and the "make-vendor" script.