brevdev / brev-go-cli

Brev CLI

Distribute to Homebrew

Step 1: bump version (see top of Makefile)

Step 2: create homebrew distribution

> API_COTTER_KEY=... make dist-homebrew

Step 3: create GitHub release

Step 4: upload resultant tar.gz to GitHub release

Step 5: copy sha256 (output from step 2) and use it in a new update to https://github.com/brevdev/homebrew-tap

Completions

To get completion to work:

brev completion bash > /usr/local/etc/bash_completion.d/brev

// this may not be needed echo "autoload -U compinit; compinit" >> ~/.zshrc

brev completion zsh > "${fpath[1]}/_brev"

brev-go-cli's Issues

Command to list all eps and URLs (could be brev list?)

Finalize basic Brev API integration

Enhance Command Context to Include Colorized Output

This looks great!

Question on uptake -- what if we changed "CommandContext" to just be "Terminal" (or "CLI"?) and wrapped some of the colorization along with the writers, e.g.:

type Terminal struct {
	out     io.Writer
	verbose io.Writer
	err     io.Writer

	Green  func(format string, a ...interface{}) string
	Yellow func(format string, a ...interface{}) string
	Red    func(format string, a ...interface{}) string
}

func NewTerminal() *Terminal {
	return &Terminal{
		out:     os.Stdout,
		verbose: os.Stdout,
		Green:   color.New(color.FgGreen).SprintfFunc(),
		Yellow:  color.New(color.FgYellow).SprintfFunc(),
		Red:     color.New(color.FgRed).SprintfFunc(),
	}
}
func (t *Terminal) Outln(message string) {
	fmt.Fprint(c.out, message+"\n")
}

func (t *Terminal) Verboseln(message string) {
	fmt.Fprint(c.verbose, message+"\n")
}

func (t *Terminal) Errln(message string) {
	fmt.Fprint(c.err, message+"\n")
}

Then uptake would look something like:

func main() {
	// all the initial setup in the root cmd tree
	t := NewTerminal()
	FooBar(t)
}

func FooBar(t *Terminal) {
	t.Outln(t.Green("Hey this is green\n") + t.Yellow("And this is yellow"))

	t.Errln(t.Red("This is an err so it's red!") + "\nBut here is some helper text that is uncolored")
}

Originally posted by @drewmalin in #42 (comment)

Get base path of current Brev project (given that the user might be deeper in the directory)

brev init to create endpoints and reference active_projects.json

Add Remote Context

Add spinners for loading

Writing to file is a string

brev push/pull

brev endpoint run JSON body

Error Handling, Error Output

brev status command

Add Endpoint

Brev init should support creating new projects (not just initializing existing ones)

getRootProjectDir should be in the localContext

Add Remove Package, Remove Variable to brevCtx

Can do later, but might be cool to have an options struct that allows this rate to be configured by the caller.

Can do later, but might be cool to have an options struct that allows this rate to be configured by the caller.

Originally posted by @drewmalin in #50 (comment)

LocalContext should read from files, saving the command code from having to do it

Colorized Output

brev diff to compare local/remote

Distribution to Homebrew

brev init

Spinners/output text

brev pull

brev env *

Figure out Endpoint Shell completion

brev package *