falcosuessgott / golang-cli-template

A general purpose golang CLI template for Github and Gitlab

Hi there 👋

Im Tom, DevOps Engineer in Berlin and interested in Linux, Go, Kubernetes and Open Source. Im based in Berlin/Germany.

👷 Check out what I'm currently working on

• kubefirst/gitops-template - a template of gitops infrastucture for consumption by kubefirst users (2 days ago)
• olOwOlo/hugo-theme-even - 🚀 A super concise theme for Hugo https://hugo-theme-even.netlify.app (2 days ago)
• FalcoSuessgott/vault-kubernetes-kms - Encrypt Kubernetes Secrets using Hashicorp Vault as the KMS Provider (5 days ago)

🌱 My latest projects

• FalcoSuessgott/comments - comments for morelly.de using https://github.com/gitalk/gitalk
• FalcoSuessgott/vault-kubernetes-kms - Encrypt Kubernetes Secrets using Hashicorp Vault as the KMS Provider
• FalcoSuessgott/hashicorp-vault-playground - Bootstrap a local Vault HA Cluster with many useful learning labs in under a minute using only terraform, docker & minikube!

🔭 Latest releases I've contributed to

• kubefirst/gitops-template (v2.4.7, 2 days ago) - a template of gitops infrastucture for consumption by kubefirst users
• stmcginnis/gofish (v0.17.0, 5 days ago) - Gofish is a Golang client library for DMTF Redfish and SNIA Swordfish interaction.
• FalcoSuessgott/vault-kubernetes-kms (v0.0.6, 2 weeks ago) - Encrypt Kubernetes Secrets using Hashicorp Vault as the KMS Provider

📜 My recent blog posts

• Git: GPG sign multiple previous commits (1 month ago)

🔨 My recent Pull Requests

• feat(k3d): refactor suggestion on kubefirst/kubefirst (4 days ago)
• fix(k3d-github): fix typo in oidc client module call on kubefirst/gitops-template (4 days ago)
• feat(envs): use utils.ParseEnvs on FalcoSuessgott/vkv (2 weeks ago)

Want your own self-generating profile page? Check out readme-scribe!

golang-cli-template's Issues

improvements #2

• add go get init and go get -u to install script
• add install deps script for pre-commit, gofumpt, ....

use go test matrix testing

add replacements to nfpm

replacements:
      darwin: Darwin
      linux: Linux
      amd64: x86_64

and add example for downloading this

Add tools file for code dependencies

Install on macOS fails with system `sed`

The system version of macOS sed behaves slightly different than Linux.

install.sh fails on macOS (12 - Monterey, but probably earlier and later too) with the following error:

sed: 1: "./cmd/version.go": invalid command code .

This works fine on Linux (or on macOS with non-system sed version) :

find . -type f -exec sed -i "s/golang-cli-template/$projectname/g" {} +
find . -type f -exec sed -i "s/FalcoSuessgott/$user/g" {} +

sed in-place replacement works slightly different on macOS: it wants an empty argument.

find . -type f -exec sed -I "" "s/golang-cli-template/$projectname/g" {} +
find . -type f -exec sed -I "" "s/FalcoSuessgott/$user/g" {} +

Annoying, I know.

See also https://stackoverflow.com/questions/7573368/in-place-edits-with-sed-on-os-x

I might get around to send a PR for this, but in case I don't here's an issue at least :-)

p.s. thank you for the project!

use github/super-linter

add mkdocs

todos

• dockerfile with golang binary
• docker build and publish ci stage (gitlab & github)
• improve usage script steps
• makefile targets documentation

github pages example

https://pages-themes.github.io/minimal/

use table pattern unit testing

fix docker build and push ci

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

add semantic releaser

`make build` returns `fatal: No names found, cannot describe anything.`

As git describe --abbrev=0 --tags fails.

Todo

• Add manpage
• Completion
• Docker goreleaser
• Goreleaser changelog
• Commitlint
• use tbc for the gitlab ci