kelseyhightower/envconfig VS awesome-actions

To configure the app I'd take a look at https://github.com/kelseyhightower/envconfig

envconfig

- Having one way of configuring the app is excellent. You can either prefer environment variables, a file, or flags. You can do what Viper does by reading the file and unmarshalling it. The built-in flag package is enough for your flag-based config needs. If you want to prefer environment variables, I prefer https://github.com/kelseyhightower/envconfig

To extract values from the system environment, I utilize envconfig, a Go package. Envconfig facilitates mapping system environment variables to a Go struct. These Go structs are exposed through a config package, enabling other parts of the application to access them.

You could prefix your env vars and use this package. https://github.com/kelseyhightower/envconfig

kelseyhightower/envconfig

Pretty much all of our services and pkgs use https://github.com/kelseyhightower/envconfig. It’s dead simple, gets out of your way, and is battle tested

https://github.com/kelseyhightower/envconfig (read config from environment variables, more succinct than viper)

Awesome Actions - A curated list of awesome things related to GitHub Actions.

Since it sounds like you're using GitHub, using GitHub Actions for any CI pipelines would be easiest. You could run terraform plan in your PRs, there's a great writeup on how to do it here. Or any unit tests, docker builds, etc. Lots of great ideas at Awesome Actions.

Here is a list of some examples you might want to check out.

A curated list of actions to use on GitHub\ (6 comments)

With the recent success of Github actions you can automate lots of things whenever something in your repos changes, e.g. automatically generate static HTML content (using hugo) and push it to some repository for which GitHub Pages has been configured. Check this awesome actions list for more use cases.

Projects: awesome-actions, intro-to-vue, cssgridgenerator, array-explorer, ecommerce-netlify