build out of cli tool

.gitignore

@@ -10,3 +10,8 @@
 
 # Output of the go coverage tool, specifically when used with LiteIDE
 *.out
+
+build
+testdata
+vault-key
+.idea

CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the maintainers of this repository before making a change.
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before submitting a Pull Request.
+2. Update the [README.md](README.md) with details of changes to the interface, this includes new environment
+   variables, exposed ports, useful file locations and container parameters.
+3. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
+   do not have permission to do that, you may request the second reviewer to merge it for you.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

Makefile

@@ -0,0 +1,42 @@
+NAME=gwvault
+
+VERSION=$$(git describe --tags --always)
+
+LDFLAGS=-ldflags "-X main.version=${VERSION}"
+
+all: tools build
+
+tools:
+	go get -u -v "github.com/mitchellh/gox"
+
+build:
+	@mkdir -p bin/
+	go get -t ./...
+	go test -v ./...
+	go build ${LDFLAGS} -o bin/${NAME} cmd/gwvault/main.go
+
+xbuild: clean
+	@mkdir -p build
+	gox \
+		-os="linux" \
+		-os="windows" \
+		-os="darwin" \
+		-arch="amd64" \
+		${LDFLAGS} \
+		-output="build/{{.Dir}}_$(VERSION)_{{.OS}}_{{.Arch}}/$(NAME)" \
+		./...
+
+package: xbuild
+	$(eval FILES := $(shell ls build))
+	@mkdir -p build/tgz
+	for f in $(FILES); do \
+		(cd $(shell pwd)/build && tar -zcvf tgz/$$f.tar.gz $$f); \
+		echo $$f; \
+	done
+
+clean:
+	@rm -rf bin/ && rm -rf build/
+
+ci: tools package
+
+.PHONY: all tools build xbuild package clean ci

README.md

@@ -1,2 +1,70 @@
-# gwvault
-`ansible-vault` CLI reimplemented in go
+# gwvault - GoodwayGroup Ansible Vault
+
+> `ansible-vault` CLI reimplemented in go
+
+`ansible-vault` is a very powerful tool and we wanted to simplifying the install and management of the tool as a standalone, cross platform tool.
+
+## Basic Usage
+
+Us in place of `ansible-vault`. All commands are reimplemented except for `encrypt_string` and `rekey` (coming soom!). The tool will default to asking for your Vault password.
+
+```
+NAME:
+   gwvault - encryption/decryption utility for Ansible data files
+
+USAGE:
+   gwvault [global options] command [command options] [arguments...]
+
+COMMANDS:
+     encrypt  encrypt file
+     decrypt  decrypt file
+     edit     edit file and re-encrypt
+     create   create a new encypted file
+     view     view contents of encrypted file
+     help, h  Shows a list of commands or help for one command
+
+GLOBAL OPTIONS:
+   --vault-password-file VAULT_PASSWORD_FILE  vault password file VAULT_PASSWORD_FILE
+   --help, -h                                 show help
+   --version, -v                              print the version
+```
+
+### Prerequisites
+
+* go v1.10+
+* make
+* [auto-changelog](https://www.npmjs.com/package/auto-changelog) (Optional. Used for managing releases)
+
+## Built With
+
+* go v1.10+
+* make
+* [github.com/mitchellh/gox](https://github.com/mitchellh/gox)
+
+## Contributing
+
+Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+
+## Versioning
+
+We employ [auto-changelog](https://www.npmjs.com/package/auto-changelog) to manage the [CHANGELOG.md](CHANGELOG.md). For the versions available, see the [tags on this repository](https://github.com/GoodwayGroup/gwvault/tags).
+
+## Authors
+
+* **Derek Smith** - [@clok](https://github.com/clok)
+
+See also the list of [contributors](https://github.com/GoodwayGroup/gwvault/contributors) who participated in this project.
+
+## License
+
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details
+
+## Acknowledgments
+
+* Thank you to [@pbthorste](https://github.com/pbthorste) for doing the heavy lifting on [avtool](https://github.com/pbthorste/avtool)
+
+## Sponsors
+
+[![goodwaygroup][goodwaygroup]](https://goodwaygroup.com)
+
+[goodwaygroup]: https://s3.amazonaws.com/gw-crs-assets/goodwaygroup/logos/ggLogo_sm.png "Goodway Group"