Skip to content

Latest commit

 

History

History
33 lines (21 loc) · 1.54 KB

DEVELOPMENT.md

File metadata and controls

33 lines (21 loc) · 1.54 KB

Development Guide for kubectl-cost

Building

The build process uses govvv to set info for the version subcommand until there is in-compiler support for getting version info. If you don't have govvv installed, you can always edit the Makefile to use go instead of govvv.

Build:

make build

Install:

If your GOPATH is default and you have /home/USERNAME/go/bin in your path, you can use make install. Otherwise:

chmod +x cmd/kubectl-cost/kubectl-cost
cp cmd/kubectl-cost /somewhere/in/your/PATH/kubectl-cost

As long as the binary is still named kubectl-cost and is somewhere in your PATH, it will be usable.

Releasing

Tag from main with a valid SemVer version (e.g. v0.2.0) that is after the most recent release. For writing release notes, you can use git log to see commits since the last release (e.g. git log v0.1.9..HEAD). There is a GitHub Actions workflow that handles building and publishing release binaries and archives to a GitHub release. It will be triggered automatically by any tag pushed that is prefixed with v.

Once the release completes, the Krew manifest should be automatically updated in the same workflow using krew-release-bot. Make sure this succeeds - the PR to krew-index should be merged automatically.